Loading...
Loading...
Found 2,167 Skills
Use when agents need to query native Notis databases with direct structured filters, sorts, and pagination through `LOCAL_NOTIS_DATABASE_QUERY`.
This skill should be used when designing multi-agent systems that need context isolation, supervisor or swarm coordination, explicit handoffs, parallel execution, or a decision on whether multiple agents are justified.
Create, refactor, shorten, or debug skills, descriptions, and reference loading. Use writing-agents-md for AGENTS.md/CLAUDE.md; excludes general documentation and READMEs.
Defines safe Git workflow conventions for agents. Use whenever creating or naming branches, inspecting or staging changes, writing commit messages, creating commits, pushing branches, force-pushing, or otherwise working with Git state.
STOP — if you were dispatched as a subagent to execute a briefed task, this skill is not for you: it governs the dispatching orchestrator only, and the mode and path rules you need are already in your brief. Do the task you were briefed with instead. Use whenever the user asks to dispatch, launch, spawn, fan out, or delegate work to an agent, subagent, worker, or coding agent in a separate git worktree — phrasing like "dispatch a subagent", "launch an agent", "fan out subagents", "parallel agents", or "use a separate worktree to implement/fix/refactor/test/review X" — or whenever two or more workers must edit the same repository concurrently without colliding. Symptoms it prevents: worktrees created from the wrong base commit, workers accidentally editing the orchestrator checkout when an isolated worktree was intended (Mode D is the sanctioned single-writer exception), Edit/Write failing outside the agent CWD, colliding diffs, shared Docker/e2e infrastructure clobbered by concurrent test runs, merged worktrees left consuming disk, and force-removed worktrees losing uncommitted work.
Create, audit, shorten, or scope AGENTS.md and CLAUDE.md instructions. Use writing-skills for on-demand skills; excludes human-facing documentation and READMEs.
v2.5.0 — Use when bootstrapping, completing, updating, or auditing project documentation, or documenting a feature/module/epic: AGENTS.md + docs/, ADRs, roadmap, docs/features/<slug>/, docs/plans/<slug>/. Triggers: "document this project", "bootstrap docs", "sync docs", "audit docs", "docs vs code", "from zero", "new feature", "nueva feature", "promové el plan", "after ark-check", "arkgate bridge", "knowledge dashboard", /documentation-manager. Intents: integrate, audit, from-zero. Feature autopilot v2; Implementation bridge opt-in; ArkGate post-gate sync; dashboard HTML; polyglot + monorepo hubs; team governance (docs/team); living claims v0 + local CI structural audit (Knowledge OS first increment toward 100×). On conflict code wins.
Use when user says "create workflow", "create a workflow", "design workflow", "orchestrate", "automate multiple steps", "coordinate agents", "multi-agent workflow". Creates orchestration workflows from natural language using Socratic questioning to plan multi-agent workflows with visualization.
Running the backend dev cycle: implements every task in a rolling-wave plan.md (ring:writing-plans format) for a Go/TS service, driving specialist agents through Gate 0 implementation/TDD, Gate 8 parallel review, and Gate 9 validation per epic, elaborating later phases at each phase boundary. Use when starting or resuming a gated backend dev cycle with a plan.md (legacy tasks.md only for cycles already in flight; new cycles need the canonical plan format). Skip for frontend (use ring:running-dev-cycle-frontend) or docs-only work.
Write agent-facing files (SKILL.md, AGENTS.md, CLAUDE.md, READMEs, runbooks) so they survive a first-time reader with no shared history. Use when creating or editing any such file, or reviewing one for noise.
Guide coding agents working in applications that consume @dune2/tools. Use when @dune2/tools is installed and the task involves API requests or TanStack Query, browser/cookie storage, Valtio state, React Context factories, prop adapters, typed field names, or precise decimal formatting/calculation. Prefer the library's existing APIs over rebuilding equivalent helpers.
This skill should be used when the user wants to "run an evaluation", "evaluate my ADK agent", "write an evalset", "debug eval scores", "compare eval results", or needs guidance on ADK (Agent Development Kit) evaluation methodology and the eval-fix loop. Covers eval metrics, evalset schema, LLM-as-judge, tool trajectory scoring, and common failure causes. Part of the Google ADK (Agent Development Kit) skills suite. Do NOT use for API code patterns (use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).