All authors
Claude Skills by allemaar
github.com/allemaar81 skills0 installs124 views
- Plan CreatePropose a phased, gated implementation plan before any work begins. Trigger when the user runs /plan-create, says "make a plan", "plan this out", "design before coding", "let's plan first", "architect this", or asks for a phased approach before implementation. Also trigger proactively when a task is complex enough that jumping straight to execution would be risky — multi-file changes, new features, architectural shifts, refactors spanning multiple components, or any task where misalignment ea...Votes: 0GitHub stars: 14
- Plan Deep DivePhase-by-phase deep inspection of any multi-phase plan — stop at each phase and assess completeness, quality, and future-readiness before advancing. Trigger when the user runs /deep-dive or asks to "do a deep dive", "inspect each phase", "look at this more carefully", or "check if we're missing anything" on an existing plan. Use plan-create to create a new plan, plan-execute to run an approved plan, and plan-phases to add gates to a plan.Votes: 0GitHub stars: 14
- Plan EvolveEvolve a target to its next version — treat what shipped as v1, plan the next iteration. The target can be a plan, a repo, a system, a document, a feature, or a skill. If a v1 plan artifact exists, evolve it; if not, the current state of the target IS v1. Trigger: 'what would v2 look like', 'evolve this', 'what's next for this', 'next iteration of this', 'plan the next version'. Use plan-deep-dive to inspect the current state, plan-execute to run the new plan, and plan-cleanup to remove artif...Votes: 0GitHub stars: 14
- Plan ExecuteApply the last approved plan exactly. Trigger when the user runs /execute or says "execute the plan", "implement this", "do it", or "go ahead" after a plan has been approved. Surface judgment calls — do not make them silently. Not /plan-create (designs the plan first) or /plan-deep-dive (inspects a plan without running it) — plan-execute runs an already-approved plan.Votes: 0GitHub stars: 14
- Plan PhasesRestructure an existing plan into phases with /verify gates after each phase and critical outcomes, plus blocking pre-action gates for safety prerequisites. Trigger when the user runs /phase-plan or asks to "add phases to this plan", "gate this plan", "restructure the plan", or "add checkpoints". Use plan-create for new plans and plan-deep-dive for inspection without restructuring.Votes: 0GitHub stars: 14
- Prime ExpandExpand a vague gap into concrete questions + named source candidates via a delegated sub-agent — caller sees only the proposed pair for confirm/edit/refuse, never the expansion reasoning. Trigger /prime-expand, "expand on this", or auto-fire on handoff receipt with a thin brief. (Not for ambient "I need to know X" phrasing — that would collide with /investigate.) Single sub-agent, single turn, ≤3 candidate-source spot-checks only. Pairs with /prime-fetch (single noisy tool call) and /prime-sw...Votes: 0GitHub stars: 14
- Prime FetchRun a noisy data-fetching tool call (Grep, Glob, WebFetch, MCP search) on the caller's behalf in a sub-agent's context — only the filtered, proof-of-work-verified digest enters the caller's window. Trigger /prime-fetch, or when a planned tool call will return mostly noise. Single sub-agent, single wave, read-only tool calls only. Pairs with /prime-expand (clarify intent first) and /prime-sweep (multi-source investigation).Votes: 0GitHub stars: 14
- Prime SweepPrime the calling agent with high-signal context from large source surfaces (multiple files, packages, folders) via parallel delegated sub-agents. Sub-agents absorb the noise; only digested findings + source:line pointers enter the caller's context. Trigger /prime-sweep, chained from /prime-expand when sources are too large, or auto-fire on handoff receipt with listed sources. Iterative with cap 3 / log 4-6 / ask 7 / max 8 waves total. Pairs with /prime-expand (clarify intent first) and /prim...Votes: 0GitHub stars: 14
- Prose AuditDiagnose semantic repetition, filler, fake structure, stock AI rhetoric, and avoidable reading load in existing text. Trigger phrases: "/prose-audit", "find the AI filler", "audit this for bloat". Not for rewriting text; use /human-rewrite after diagnosis.Votes: 0GitHub stars: 14
- ReflectLightweight cognitive pause — surface assumptions, uncertainty, and what you'd do differently. No gate, no enforcement, no artifacts required. Trigger when the user runs /reflect or wants to step back and think before continuing. Not /verify (formal gate) or /ask-gate (question triage) — reflect is freeform thinking with no gate.Votes: 0GitHub stars: 14
- Route TaskEXPERIMENTAL capability-routing rubric — score a task on five task-readable axes (Risk, Uncertainty, Scope, Coupling, Verification) to derive WHO should execute (capability band 0–3) and HOW HARD they should try (volume 0–24), plus an evidence-derived plan gate. Recommends, never mandates; bands name ladder positions, never models, self-resolved from the runtime's own live roster; any doubt means session model. Trigger when the user runs /route-task, asks "which model should handle this", "ho...Votes: 0GitHub stars: 14
- Self ImproveThe Self-Improvement Protocol (SIP). After a participating skill runs, detect concrete signals that the skill itself could be better — ambiguous instructions, an uncovered edge case, a misfired rule, a stale cross-reference, a user correction — and propose a specific diff to it, surfaced for approval and never auto-applied. Conservative by default: silent unless a ready, blocking, or recurring fix exists. Trigger via /self-improve, or automatically when a self-improvable skill completes. Not ...Votes: 0GitHub stars: 14
- Skills HelpThe skills library menu — every skill grouped by family, each with a one-line description and a dual-doc/single-doc marker; pass a family name to drill into one family in full detail. Trigger with /skills-help, "list my skills", "which skill for X", "skills menu", "what skills do I have". Not /new-skill-creator (which scaffolds a new skill).Votes: 0GitHub stars: 14
- Synthesize InitOpt-in installer for a minimal standing /synthesize route in existing agent directive files. Shows exact per-file diffs, requires approval, backs up, writes atomically, verifies, and supports removal.Votes: 0GitHub stars: 14
- SynthesizeTurn agent output into faithful, scannable, purpose-matched delivery. Use before writing or to restructure existing text. Routes to one need-specific shape without loading unrelated examples.Votes: 0GitHub stars: 14
- VerifyFormal phase gate — checks intent, plan, and execution artifacts for drift, then actively re-checks each load-bearing claim against its source (an agent's self-report of having checked is not evidence). Requires the intent and execution artifacts (the plan is optional; an absent plan short-circuits to a plan-not-found verdict). Produces structured output. Trigger when the user runs /verify or needs to decide whether to proceed to the next phase. Not /double-check (quick re-check of one claim)...Votes: 0GitHub stars: 14
- Yon ReadRead, interpret, or explain existing YON content. Trigger on any .yon file, YON snippet (lines with @TAG|...|... patterns), or when the user says "read this YON", "what does this YON mean", "explain this @DOC/@RULE/@STEP", "summarize this YON", "interpret this record". Do NOT trigger for generic format questions ("what is YON?") with no YON content present — and do not trigger when the user wants to *write* YON (use yon-write).Votes: 0GitHub stars: 14
- Yon WriteYON Writing & Compilation Mode. Use when creating, generating, converting, or writing YON content. Triggers on: "write YON", "convert to YON", "create a .yon file", "encode this as YON", "YON format", or any request where the expected output is YON records. Also triggers when unstructured content should be structured into YON even without explicit keyword — e.g., working in a YON project. Use yon-read instead when reading, interpreting, explaining, or summarizing existing YON.Votes: 0GitHub stars: 14
- Gate FixturesIdentical in shape to `missing-footer-skill.md`, but the last block is the verbatim two-line blockquote. A green run here means the check read the file and found the footer, not that it never looked.Votes: 0GitHub stars: 14
- Gate FixturesThe body below opts into the contract by naming `human-output/SKILL.md`, so the footer is mandatory. What follows the citation is a PARAPHRASE, not the verbatim blockquote — which is exactly the drift a growing family produces.Votes: 0GitHub stars: 14
- Directives AuditAudit or explicitly housekeep agent directives for authority, scope, safety, density, routing, drift, and consumed parity. Trigger on /directives-audit or "boil my directives". Not for skills or prose.Votes: 0GitHub stars: 14
- Skills AuditAudit or explicitly housekeep an Agent Skill or library for instruction quality, routing, decomposition, portability, dependencies, and consumed behavior. Trigger on /skills-audit or "boil this skill". Not for directives or prose.Votes: 0GitHub stars: 14
- Headless ClaudeRun a bounded, observable Claude Code headless task with explicit model, least-privilege tools, and preserved authorization. Trigger on /headless-claude, "run Claude headlessly", "use Claude -p", or "supervise a Claude harness". Not for changing Claude authentication or installing Claude Code.Votes: 0GitHub stars: 14
- Headless CodexRun Codex CLI safely in bounded non-interactive workflows, including /headless-codex, "run Codex headlessly", and "automate Codex CLI". Not for creating skills or changing Codex configuration.Votes: 0GitHub stars: 14
- Headless GeminiRun bounded Gemini tasks through Antigravity CLI (agy). Trigger on /headless-gemini, "run Gemini headlessly", or "supervise agy". Not for the separate gemini CLI, installation, authentication changes, or API-key setup.Votes: 0GitHub stars: 14
- Headless GrokRun bounded Grok Build coding-agent tasks through the official grok CLI. Trigger on /headless-grok, "run Grok headlessly", or "supervise grok -p". Not for installation, authentication changes, API-key setup, or consumer chat automation.Votes: 0GitHub stars: 14
- Headless ModelsCompare providers, models and effort against task quality, cost, latency and local availability. Trigger on /headless-models, "which model should I use", or "update all model maps". Read-only selection. Use headless-update-models to refresh the family.Votes: 0GitHub stars: 14
- Headless Update ModelsRefresh provider models, effort, cost and benchmark evidence across all supported headless skills. Use /headless-update-models or "update headless models". For read-only selection use headless-models.Votes: 0GitHub stars: 14
- Headless UsageRead current quota, usage and reset times across Codex, Claude Code, Antigravity and Grok Build. Use /headless-usage, "show my quotas", or "how much usage is left". Returns a dated result for every requested harness, including unavailable data.Votes: 0GitHub stars: 14
- Write Copy Event VideoCreate three independent event-video copy variants, cross-examine them, and write a fourth synthesis with voiceover handoff. Use /write-copy-event-video or "write an event promo script". Drafting only; no media generation or publishing.Votes: 0GitHub stars: 14
- Write CopyRoute promotional copy to a topic specialization. Use /write-copy, "write campaign copy", or "write event copy". For a known event video use write-copy-event-video directly; for faithful prose repair use human-rewrite.Votes: 0GitHub stars: 14