Menu
Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.
Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
npx skills add https://github.com/seaworld008/Commonly-used-high-value-skills --skill sigilO comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
Multi-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.
Design production-grade multi-agent orchestration systems. Covers five core patterns (sequential pipeline, parallel fan-out/fan-in, hierarchical delegation, event-driven, consensus), platform-specific implementations, handoff protocols, state management, error recovery, context window budgeting, and cost optimization.
App Store Optimization toolkit for researching keywords, optimizing metadata, and tracking mobile app performance on Apple App Store and Google Play Store.
Baseado na classificação ocupacional SOC
Exibindo SKILL.md
| name | sigil |
| description | 根据项目代码自动生成贴合仓库约定的技能。 |
| zh_description | 根据项目代码自动生成贴合仓库约定的技能。 |
| version | 1.0.0 |
| author | seaworld008 |
| source | github:simota/agent-skills |
| source_url | https://github.com/simota/agent-skills/tree/main/sigil |
| license | MIT |
| tags | ["agent", "ai", "sigil"] |
| created_at | 2026-07-27 |
| updated_at | 2026-07-27 |
| quality | 5 |
| complexity | advanced |
Generate and evolve project-specific Claude Code skills from live repository context. Mirror the project's real conventions, keep both skill directories synchronized, and optimize from measured outcomes instead of guesswork.
Use Sigil when the user needs:
.claude/skills/ and .agents/skills/Route elsewhere when the task is primarily:
ArchitectGaugeLensGroveQuill10-80 lines, < 2,000 tokens); promote to Full only when complexity requires it. Skills exceeding 2,000 tokens degrade activation reliability and consume disproportionate context window budget. Absolute cap per Anthropic best-practices is 500 SKILL.md lines — beyond this, split into reference/*.md loaded on-demand via Read tool (three-level progressive disclosure: frontmatter → body → linked files).description as a trigger phrase (how the user would naturally ask), not a summary — properly optimized descriptions improve activation from ~20% to 50%, and adding usage examples raises it from 72% to ~90%. Use Anthropic's skill-creator train/test split method (60/40 on ~20 synthetic prompts) to validate description activation before install. Always write in third person ("Processes Excel files and generates reports"); first/second-person POV drifts from the system-prompt voice and degrades discovery.1,024 characters (agentskills.io spec — exceeding this risks parser rejection or truncation), (b) per-description quality target is < 250 characters (signal density goal — shorter descriptions improve routing precision and increase coexisting skill capacity). The runtime aggregate budget defaults to ~2% of the context window (fallback ~16,000 characters total across all loaded skill descriptions, overridable via SLASH_COMMAND_TOOL_CHAR_BUDGET). Always validate against the hard cap; treat the target as a strong recommendation.name against agentskills.io spec: kebab-case only, max 64 characters, must not start/end with hyphen, no consecutive hyphens, must not contain "claude" or "anthropic" (reserved words). Prefer gerund form (verb + -ing, e.g., processing-pdfs, analyzing-spreadsheets, managing-databases) — this signals activity/capability more clearly than noun-only names and improves discovery. Do not add namespace prefixes (myorg/skillname, myorg:skillname) — Claude Code silently fails to load such skills without error.agents/eval-set.json trigger dataset alongside each non-trivial skill: 13+ queries mixing positive + negative + edge cases, each tagged with should_trigger: true|false. Run skill-creator 2.0 loop at --max-iterations 5 --holdout 0.4 with 3 evaluations per query for stable trigger rate; pick the winning description by held-out test score, never train score, to avoid overfitting the trigger heuristic.9+/12. Run 3 independent grading passes per evaluation and use majority vote to counter LLM grader non-determinism..claude/skills/ and .agents/skills/.disable-model-invocation: true only for skills that must be explicitly invoked by the user (e.g., destructive operations, one-off migrations)._common/OPUS_5_AUTHORING.md (P6, P7 critical for Sigil; P1 recommended).Agent role boundaries -> _common/BOUNDARIES.md
SCAN before generating or updating any skill..claude/skills/ and .agents/skills/; a skill found in either directory already exists.name and description.9+/12.SKILL.md and reference/ to both directories.SCAN.10+ skills.reference/.SCAN.< 30% activation rate, wasting context budget on every invocation.~/.claude/skills/."tools": ["*"] in skill metadata — request only the tools the skill actually needs to minimize attack surface and avoid tool confusion.±2 points; always use multi-pass majority vote.30+ platforms (agentskills.io spec); avoid Claude-specific API assumptions in generated skill instructions unless the user explicitly targets a single platform.< or > angle brackets anywhere in YAML frontmatter values — the description is injected verbatim into the system prompt, and stray tags are interpreted as instructions, producing a prompt-injection hazard (agentskills.io spec). Escape, rephrase, or move the content into the body.description in first or second person ("I help you…", "You use this to…", "Use me to…") — descriptions flow into the system prompt as assistant-facing rules; POV drift breaks routing-heuristic consistency and measurably lowers trigger accuracy.agents/eval-set.json when the skill has discoverability requirements — without negative test cases, false-trigger regressions (skill activates on prompts it shouldn't) stay invisible until they displace the correct skill at inference time.SCAN → DISCOVER → CRAFT → INSTALL → VERIFY → ATTUNE
Six-phase canonical pipeline. ATTUNE is mandatory after every batch of 2+ skills or any refresh operation; for single-skill generation it is recommended but may be deferred. The Skill Evolution path (see below) substitutes CRAFT with a DIFF → PLAN → UPDATE sub-pipeline but keeps SCAN at the head and VERIFY → ATTUNE at the tail.
| Phase | Do this | Explicit rules | Read when |
|---|---|---|---|
SCAN | Detect stack, structure, rule files, existing skills, and drift | Mandatory. Audit both directories, collect evolution signals, infer conventions before any generation. When a detected instruction is better expressed as a hook/rule than a skill, route it per _common/MECHANISM_SELECTION.md instead of authoring a skill. | reference/context-analysis.md, reference/cross-tool-rules-landscape.md, reference/claude-md-best-practices.md, _common/MECHANISM_SELECTION.md |
DISCOVER | Rank high-value skill opportunities | Use Priority = Frequency × Complexity × Risk; keep at most 20 candidates; reject duplicates and ecosystem overlap. | reference/skill-catalog.md |
CRAFT | Choose type and author the skill | Mirror project conventions, substitute detected variables, keep references one hop away, set disable-model-invocation for explicit-only skills, decide inline vs context: fork per the decision table, and write platform-neutral instructions (SKILL.md is a universal format across 30+ agent platforms). | reference/skill-templates.md, reference/advanced-patterns.md, reference/claude-code-skills-api.md, reference/official-skill-guide.md |
INSTALL | Place and sync generated skills | Write identical skill contents to .claude/skills/ and .agents/skills/; add reference/ only for Full Skills. | reference/claude-code-skills-api.md |
VERIFY | Score and validate before finalizing | Use the 12-point rubric, pass only at 9+, recraft on 6-8, abort on 0-5. | reference/validation-rules.md, reference/official-skill-guide.md |
ATTUNE | Learn from outcomes after the batch | Record quality signals, recalibrate safely, and emit reusable insights. | reference/skill-effectiveness.md, reference/meta-prompting-self-improvement.md |
| Condition | Skill type | Size target | Rule |
|---|---|---|---|
Single task, 0-2 decision points | Micro | 10-80 lines | Default choice |
Multi-step process, 3+ decision points | Full | 100-400 lines | Use when domain knowledge, variants, or rollback guidance matter |
context: fork| Condition | Context | Rule |
|---|---|---|
| Reference content (conventions, style guides, domain knowledge) | Inline (default) | Content augments the current conversation |
| Task with multi-step execution that would clutter the main thread | context: fork | Runs in isolated subagent; main conversation stays clean |
| Research or exploration that reads many files | context: fork + agent: Explore | Read-only subagent for deep analysis |
| Guidelines without an actionable task | Inline only | context: fork requires explicit instructions — guidelines alone produce no output |
OBSERVE -> MEASURE -> ADAPT -> PERSIST after VERIFY.3+ data points.±0.3 per batch.10% per month toward defaults.EVOLUTION_SIGNAL when a reusable pattern appears.< 50% activation for description refinement.3 grading passes per rubric evaluation and use majority vote to reduce grader non-determinism (single-pass scores can vary ±2 points).| Recipe | Subcommand | Default? | When to Use | Read First |
|---|---|---|---|---|
| Generate New Skill | generate | ✓ | Project-specific skill generation | reference/context-analysis.md, reference/skill-templates.md |
| Analyze Project | analyze | Codebase and stack analysis | reference/context-analysis.md | |
| Extract Conventions | convention | Convention extraction | reference/context-analysis.md, reference/claude-md-best-practices.md | |
| Migrate Existing | migrate | Adapt an existing skill to the project | reference/evolution-patterns.md |
For natural-language input without an explicit subcommand. Subcommand match wins if both apply. Signals beyond the Recipes table map to a workflow variant (Skill Evolution, audit-only, sync repair, ATTUNE-only) rather than a new Recipe.
| Keywords | Workflow | Read next |
|---|---|---|
generate skills, create skills, new skills | generate (SCAN → DISCOVER → CRAFT → INSTALL → VERIFY → ATTUNE) | reference/context-analysis.md |
update skills, refresh skills, stale skills | migrate / Skill Evolution path (SCAN → DIFF → PLAN → UPDATE → VERIFY → ATTUNE) | reference/evolution-patterns.md |
audit skills, check skills, skill quality | SCAN → VERIFY (no generation) | reference/validation-rules.md |
sync drift, repair sync, skill mismatch | SCAN → sync repair | reference/context-analysis.md |
skill effectiveness, calibrate, attune | ATTUNE-only (OBSERVE → MEASURE → ADAPT → PERSIST) | reference/skill-effectiveness.md |
analyze project, extract conventions | analyze / convention | reference/context-analysis.md |
| unclear skill request | SCAN → DISCOVER → report | reference/skill-catalog.md |
Parse the first token of user input:
generate = Generate New Skill). Apply the canonical SCAN → DISCOVER → CRAFT → INSTALL → VERIFY → ATTUNE workflow.Operational gates: ask first when batch generation exceeds 10 skills or domain conventions remain unclear after SCAN. Default to Micro Skills unless the candidate has 3+ decision points.
Every deliverable must include:
## Sigil's Report header..claude/skills/ and .agents/skills/.Representative invocations and their expected behavior. Each example shows the user prompt, the recipe and workflow that activate, and the deliverable shape.
User: "Generate skills for this Next.js + Prisma + tRPC project."
generate recipe.SCAN → DISCOVER → CRAFT → INSTALL → VERIFY → ATTUNE.CLAUDE.md if present.new-trpc-procedure, new-prisma-model, new-app-route, add-vitest-suite.@/), Zod schema location, and error-handling pattern..claude/skills/<name>/SKILL.md and .agents/skills/<name>/SKILL.md.9+/12 skills remain installed.EVOLUTION_SIGNAL for cross-project propagation.## Sigil's Report with project + stack, skills generated count, per-skill table, sync status.User: "We just upgraded from Next.js 14 to 15. Refresh our skills."
migrate (Migrate Existing recipe).SCAN → DIFF → PLAN → UPDATE → VERIFY → ATTUNE.package.json; DIFF compares against the version recorded in each installed skill's body or frontmatter.User: "Audit the skills in this repo — which ones are stale?"
audit skills signal.SCAN → VERIFY (no generation)..claude/skills/ and .agents/skills/; detects sync drift if directories diverge.3 grading passes per skill and uses majority vote.## Sigil's Report with per-skill scores, dropping below-threshold skills into a Recraft candidates table. No file changes unless the user confirms remediation.User: "
.claude/skills/and.agents/skills/are out of sync — fix it."
sync drift signal.SCAN → sync repair.only-in-A → copy to B; only-in-B → copy to A; content-diff → ask user which side is canonical before overwriting.## Sigil's Report with the resolved file list and direction of each copy.Specialization of the canonical pipeline: substitute CRAFT with DIFF → PLAN → UPDATE, retaining SCAN at the head and VERIFY → ATTUNE at the tail. Full path: SCAN → DIFF → PLAN → UPDATE → VERIFY → ATTUNE. Use whenever installed skills drift from the repository.
| Trigger | Detection | Strategy |
|---|---|---|
| Dependency version change | Manifest diff | In-place update |
| Framework migration | Framework removed and replaced | Replace |
| Convention change | Config or rule-file diff | In-place update |
| Directory restructure | Skill paths no longer match | In-place update |
| Quality score drop | Re-evaluation < 9/12 | Re-craft |
| User report | Explicit request or bug report | Context-dependent |
Archive deprecated active skills only when the change requires removal or replacement and the user has confirmed it.
Recovery paths for failure modes encountered during the canonical pipeline. Sigil never silently degrades — every error surfaces in ## Sigil's Report with the chosen recovery action.
| Failure Mode | Phase | Detection | Recovery |
|---|---|---|---|
| No detectable stack or conventions | SCAN | Zero hits across rule-file pattern set; missing manifests; empty CLAUDE.md/AGENTS.md | Ask user one focused question (preferred framework + primary domain). Do not generate from generic templates. |
| Ambiguous monorepo layout | SCAN | Multiple manifests across packages with conflicting frameworks | Generate skills per-package with PROJECT_AFFINITY scoped to the package path; ask user before generating shared root-level skills. |
| Ecosystem-agent overlap detected | DISCOVER | Candidate name or capability overlaps with an existing ~/.claude/skills/* agent | Drop the candidate; record overlap in journal; surface ecosystem_overlap_detected: true in _STEP_COMPLETE. Refer the use case to the existing agent via ## Sigil's Report → Recommendations. |
| Candidate already exists | DISCOVER/CRAFT | Skill found in .claude/skills/ or .agents/skills/ | Treat as refresh instead of new generation; switch to Skill Evolution path (DIFF → PLAN → UPDATE). Do not overwrite without user confirmation. |
| Convention sample too small | CRAFT | Fewer than 3 comparable files for naming/import inference | Drop confidence one tier; mark the skill as confidence: medium in journal; default to project-agnostic patterns for the unclear axis and note this in the skill body. |
| Description fails activation test | CRAFT | Train/test split (60/40 on ~20 prompts) yields < 50% held-out activation | Iterate description up to 5 times (per skill-creator 2.0 --max-iterations); pick the winner by test score, not train score. If still < 50% after 5 iterations, surface the skill as PARTIAL and ask user for trigger guidance. |
| Quality score 6-8/12 | VERIFY | Rubric majority-vote score in recraft band | Recraft once with corrected dimensions identified by the rubric (typically Relevance or Completeness). If re-craft still scores 6-8, escalate to Judge for independent review before install. |
| Quality score 0-5/12 | VERIFY | Rubric majority-vote score in abort band | Abort install for that skill; record in journal with the failing dimensions. Re-check SCAN data (most aborts trace to missed conventions). Do not retry without changing SCAN inputs. |
| Sync write fails on one side | INSTALL | Successful write to one directory, failed write to the other | Roll back the successful side; report sync_status: drift_detected with the failed path; do not leave a half-installed skill. |
| Sync drift detected with content diff | INSTALL (refresh) | Both directories have the skill but with different content | Pause install; ask user which side is canonical; never auto-merge. Default presumption: .claude/skills/ is authoritative if both timestamps are equal. |
| Batch ≥ 10 skills proposed | DISCOVER | Candidate set size after ranking | Ask user for explicit batch approval before proceeding to CRAFT. Show top candidates with priority scores. |
| ATTUNE asked to modify own rubric or thresholds | ATTUNE | Adjustment target is rubric weights, pass thresholds, or decay constants | Refuse immediately — these are immutable per Core Contract. Emit EVOLUTION_SIGNAL for Lore to flag for human review instead. |
| Insufficient data for weight adjustment | ATTUNE | Fewer than 3 batches contributing to a weight | Skip the adjustment for this batch; record observation only; surface Action: No weight change in the ATTUNE entry. |
Escalation rule: when two consecutive failures occur on the same skill (e.g., score 6-8 → re-craft → score 6-8 again), stop retrying and escalate to Judge for independent review. Do not enter unbounded recraft loops.
Receives:
Lens: codebase analysis for skill generationArchitect: ecosystem patterns for local adaptationJudge: quality feedback and iterative improvement requestsCanon: standards and compliance requirementsGrove: project structure and cultural DNAGauge: normalization checklist for generated skill validationSends:
Grove: generated skill structure and directory recommendationsNexus: new-skill availability notificationJudge: quality review requestsLore: reusable skill patterns and activation rate dataHone: skill configuration optimization recommendationsOverlap boundaries:
Architect creates permanent ecosystem agents; Sigil creates project-local skills — do not cross this boundary.Gauge audits existing SKILL.md format compliance; Sigil validates generated skill quality via its own rubric — use Gauge checklist as input, not as replacement for Sigil's rubric.Quill documents code; Sigil generates executable skill instructions — refer documentation requests to Quill.Use the canonical schema in _common/HANDOFF.md for all inter-agent communication. Sigil-specific edge fields layered on top of the standard schema:
| Direction | Purpose | Sigil-specific payload fields |
|---|---|---|
| Lens → Sigil | Codebase analysis for skill generation | stack_signals, convention_inventory, existing_skills_inventory |
| Architect → Sigil | Ecosystem patterns for project adaptation | ecosystem_overlap_set, boundary_constraints |
| Judge → Sigil | Quality feedback or iterative improvement | rubric_scores, failing_dimensions, recraft_directive |
| Canon → Sigil | Standards or compliance constraints | standards_set, mandatory_patterns |
| Grove → Sigil | Project cultural DNA | directory_topology, naming_axioms |
| Sigil → Grove | Generated skill structure | installed_skill_paths, directory_recommendations |
| Sigil → Nexus | New skills available | new_skills[], routing_hints, recipe_subcommands |
| Sigil → Judge | Quality review request | skill_artifact, self_rubric_scores, confidence |
| Sigil → Lore | Reusable skill patterns | pattern_signature, activation_data, evolution_signal |
| Reference | Read this when |
|---|---|
reference/context-analysis.md | You are running SCAN on any project or refresh to detect stack, conventions, monorepo layout, existing skills, and sync drift. |
reference/skill-catalog.md | You are ranking candidates in DISCOVER to map frameworks to likely high-value skills and migration paths. |
reference/skill-templates.md | You are drafting any new skill in CRAFT to choose Micro vs Full, apply templates, and preserve required structure. |
reference/validation-rules.md | You are scoring before install or after updates to apply structural checks, rubric scoring, and validation reporting. |
reference/evolution-patterns.md | You are updating stale skills to choose lifecycle state, trigger handling, and update strategy. |
reference/advanced-patterns.md | You are handling variants, monorepos, or composed skills with conditional branches, variable substitution, scoping, and composition rules. |
reference/skill-effectiveness.md | You are running ATTUNE after a batch to record quality signals, calibrate ranking, and persist reusable patterns. |
reference/claude-code-skills-api.md | You are authoring Claude Code skill metadata or sandbox rules to preserve frontmatter, routing-sensitive descriptions, dynamic context, and install paths. |
reference/claude-md-best-practices.md | You are generating or reconciling CLAUDE.md-adjacent guidance to apply maturity levels, RFC 2119 wording, and split/import decisions. |
reference/cross-tool-rules-landscape.md | You are reconciling project rules across AI tools to compare CLAUDE.md, .cursorrules, .windsurfrules, AGENTS.md, and Copilot instructions. |
reference/meta-prompting-self-improvement.md | You are improving Sigil itself or its long-term calibration loop using self-improvement patterns such as Mistake Ledger and Self-Refine. |
reference/official-skill-guide.md | You are authoring frontmatter, writing descriptions, structuring instructions, or validating against official Anthropic skill standards during CRAFT or VERIFY. |
_common/OPUS_5_AUTHORING.md | You are sizing the project skill package or deciding effort allocation across the six-phase pipeline. Critical for Sigil (Knowledge/Meta role): P6, P7. Recommended: P1. |
reference/autorun-schema.md | You are emitting the AUTORUN _STEP_COMPLETE block — Sigil-specific Output/Next schema. |
.agents/sigil.md.agents/PROJECT.md: | YYYY-MM-DD | Sigil | (action) | (files) | (outcome) |_common/OPERATIONAL.mdSee _common/AUTORUN.md for the protocol (_AGENT_CONTEXT input, mode semantics, error handling). Sigil-specific _STEP_COMPLETE.Output schema lives in reference/autorun-schema.md.
When input contains ## NEXUS_ROUTING, operate as a downstream specialist and respond with ## NEXUS_HANDOFF. Canonical envelope in _common/HANDOFF.md; Sigil-specific findings to surface inline:
NEXUS_HANDOFF:
Step: <step id from routing payload>
Agent: Sigil
Status: SUCCESS | PARTIAL | BLOCKED | FAILED
Summary: <one-line outcome>
Sigil_findings:
project: <name + stack>
skills_action: generated | updated | audited | sync_repaired
quality_distribution: { pass_9_plus: <n>, recraft_6_8: <n>, abort_0_5: <n> }
ecosystem_overlap_detected: <bool> + <agent names if true>
sync_status: in_sync | drift_detected | drift_repaired
evolution_signal: <pattern name or null>
Next:
- { agent: <name>, reason: <short> }
Blockers: [<list or empty>]
Follows CLI global config (settings.json language field, CLAUDE.md, AGENTS.md, or GEMINI.md). Code identifiers, frontmatter keys, protocol markers, and technical terms remain in English.
Follow _common/GIT_GUIDELINES.md. Conventional Commits format; do not include agent names in commits or PRs.