Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
arif-init-wrapper
Universal session auto-anchor for ALL agent vendors on arifOS VPS — Codex, Claude, Gemini, Kimi, OpenCode, Aider, Copilot, and future agents
ariffazil/arifOS 39
-
agi-autonomous-controller
AGI-level autonomous controller — self-healing, self-optimizing, constitutionally governed by arifOS F1-F13
ariffazil/arifOS 39
-
mcp-config-separation
ariffazil/arifOS 39
-
drift-watcher
Periodic knowledge freshness checker: detects when local configs, runbooks, or agent knowledge have drifted from the latest official docs. Reduces the stale-knowledge paradox over time. Use when: (1) periodic health checks or heartbeat runs, (2) before major operations, (3) user asks 'am I up to date', 'check for updates', 'is anything outdated', (4) after a software upgrade to verify configs still match new docs.
ariffazil/arifOS 39
-
MCP_CONFIG
ariffazil/arifOS 39
-
config-guardian
Universal governed config co-pilot. Before ANY change to ANY system: (1) check latest docs and running version (docs-first), (2) propose as diff with risk analysis, never apply directly (propose-only), (3) log every change with evidence and rollback (change ledger). Works for OpenClaw, Docker, PostgreSQL, Nginx, arifOS, or any software. Triggers on: 'change config', 'fix settings', 'update', 'propose patch', 'explain config', 'validate config', 'why did we change X'. Enforces propose-only workflow — human applies via git.
ariffazil/arifOS 39
-
drift-watcher
Periodic knowledge freshness checker: detects when local configs, runbooks, or agent knowledge have drifted from the latest official docs. Reduces the stale-knowledge paradox over time. Use when: (1) periodic health checks or heartbeat runs, (2) before major operations, (3) user asks 'am I up to date', 'check for updates', 'is anything outdated', (4) after a software upgrade to verify configs still match new docs.
ariffazil/arifOS 39
-
config-guardian
Universal governed config co-pilot. Before ANY change to ANY system: (1) check latest docs and running version (docs-first), (2) propose as diff with risk analysis, never apply directly (propose-only), (3) log every change with evidence and rollback (change ledger). Works for OpenClaw, Docker, PostgreSQL, Nginx, arifOS, or any software. Triggers on: 'change config', 'fix settings', 'update', 'propose patch', 'explain config', 'validate config', 'why did we change X'. Enforces propose-only workflow — human applies via git.
ariffazil/arifOS 39
-
arifOS Agent Induction
The mandatory operational guide and metabolic flow for agents interacting with arifOS. Ditempa Bukan Diberi.
ariffazil/arifOS 39
-
agentic-governance
Hardened constitutional governance — F1-F13 floor enforcement with Quad-Witness consensus for all actions
ariffazil/arifOS 39
-
git-sync
Git operations on VPS repos — status, commit, push, pull, diff, branch management
ariffazil/arifOS 39
-
vps-docker
Full VPS Docker status — all containers, resource usage, arifOS health
ariffazil/arifOS 39
-
notion
Notion workspace — read/write pages, databases, search, create tasks via Notion API
ariffazil/arifOS 39
-
health-probe
Health probes for both sides of the AGI stack — openclaw + arifOS MCP
ariffazil/arifOS 39
-
google-workspace
Gmail, Google Calendar, Drive, Sheets via Google APIs
ariffazil/arifOS 39
-
figma-create-new-file
Create a new blank Figma file. Use when the user wants to create a new Figma design or FigJam file, or when you need a new file before calling use_figma. Handles plan resolution via whoami if needed. Usage — /figma-create-new-file [editorType] [fileName] (e.g. /figma-create-new-file figjam My Whiteboard)
figma/mcp-server-guide 886
-
figma-generate-library
Build or update a professional-grade design system in Figma from a codebase. Use when the user wants to create variables/tokens, build component libraries, set up theming (light/dark modes), document foundations, or reconcile gaps between code and Figma. This skill teaches WHAT to build and in WHAT ORDER — it complements the `figma-use` skill which teaches HOW to call the Plugin API. Both skills should be loaded together.
figma/mcp-server-guide 886
-
figma-implement-design
Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions "implement design", "generate code", "implement component", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.
figma/mcp-server-guide 886
-
figma-code-connect
Creates and maintains Figma Code Connect template files that map Figma components to code snippets. Use when the user mentions Code Connect, Figma component mapping, design-to-code translation, or asks to create/update .figma.js files.
figma/mcp-server-guide 886
-
figma-create-design-system-rules
Generates custom design system rules for the user's codebase. Use when user says "create design system rules", "generate rules for my project", "set up design rules", "customize design system guidelines", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.
figma/mcp-server-guide 886
-
figma-use
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.
figma/mcp-server-guide 886
-
figma-generate-design
Use this skill alongside figma-use when the task involves translating an application page, view, or multi-section layout into Figma. Triggers: 'write to Figma', 'create in Figma from code', 'push page to Figma', 'take this app/page and build it in Figma', 'create a screen', 'build a landing page in Figma', 'update the Figma screen to match code'. This is the preferred workflow skill whenever the user wants to build or update a full page, screen, or view in Figma from code or a description. Discovers design system components, variables, and styles via search_design_system, imports them, and assembles screens incrementally section-by-section using design system tokens instead of hardcoded values.
figma/mcp-server-guide 886
-
java-fundamentals
Master core Java programming - syntax, OOP, collections, streams, and exception handling
pluginagentmarketplace/custom-plugin-java 28
-
java-microservices
Build microservices - Spring Cloud, service mesh, event-driven, resilience patterns
pluginagentmarketplace/custom-plugin-java 28