Use when capturing a solved problem as categorized documentation with YAML frontmatter for fast lookup
From clavainnpx claudepluginhub mistakeknot/interagency-marketplace --plugin clavainThis skill is limited to using the following tools:
SKILL-compact.mdassets/critical-pattern-template.mdassets/resolution-template.mdreferences/yaml-schema.mdschema.yamlSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Ingests video/audio from files, URLs, RTSP, desktop; indexes/searches moments with timestamps/clips; transcodes/edits timelines (subtitles/overlays/dubbing); generates assets and live alerts.
Purpose: Document solved problems as searchable institutional knowledge in category-organized single-file markdown with enum-validated YAML frontmatter.
Auto-invoke after: "that worked", "it's fixed", "working now", "problem solved", "that did it" ā OR via /clavain:compound.
Non-trivial only (multiple attempts, tricky debugging, non-obvious solution). Skip typos, obvious syntax errors, trivial fixes.
Extract from conversation:
BLOCKING: If module name, exact error, or resolution steps are missing, ask and WAIT:
I need a few details to document this properly:
1. Which module had this issue? [ModuleName]
2. What was the exact error message or symptom?
[Continue after user provides details]
grep -r "exact error phrase" docs/solutions/
ls docs/solutions/[category]/
If similar found, present and WAIT:
Found similar issue: docs/solutions/[path]
1. Create new doc with cross-reference (recommended)
2. Update existing doc (only if same root cause)
3. Other
Choose (1-3): _
If no match, proceed to Step 4 without user interaction.
Format: [sanitized-symptom]-[module]-[YYYYMMDD].md ā lowercase, hyphens for spaces, no special chars, <80 chars.
Examples: missing-include-BriefSystem-20251110.md, webview-crash-on-resize-Assistant-20251110.md
Load schema.yaml and classify against enums in yaml-schema.md. All required fields must be present and match allowed values exactly.
BLOCK until valid:
ā YAML validation failed
Errors:
- problem_type: must be one of schema enums, got "compilation_error"
- severity: must be one of [critical, high, medium, low], got "invalid"
- symptoms: must be array with 1-5 items, got string
Please provide corrected values.
mkdir -p "docs/solutions/${CATEGORY}" then write file using assets/resolution-template.mdlastConfirmed (YYYY-MM-DD), provenance (independent or primed), review_count: 0If similar issues found in Step 3, add - See also: [$FILENAME]($REAL_FILE) to the similar doc.
If 3+ similar issues exist, append to docs/solutions/patterns/common-solutions.md:
## [Pattern Name]
**Common symptom:** [Description]
**Root cause:** [Technical explanation]
**Solution pattern:** [General approach]
**Examples:** [links]
Critical pattern hint (if severity=critical, affects multiple modules or foundational stage, non-obvious): add note in decision menu ā š” This might be worth adding to Required Reading (Option 2). NEVER auto-promote.
When user selects Option 2, use assets/critical-pattern-template.md and number sequentially in docs/solutions/patterns/critical-patterns.md.
Present and WAIT for response:
ā Solution documented
File: docs/solutions/[category]/[filename].md
What's next?
1. Continue workflow (recommended)
2. Add to Required Reading ā promote to critical-patterns.md
3. Link related issues
4. Add to existing skill
5. Create new skill
6. View documentation
7. Other
Option 1: Return to calling workflow.
Option 2: Extract pattern ā format as ā WRONG / ā
CORRECT with code ā add to docs/solutions/patterns/critical-patterns.md ā cross-reference ā confirm.
Option 3: Prompt for filename/description ā search ā add cross-reference to both docs ā confirm.
Option 4: Prompt for skill name ā determine which reference file (resources.md, patterns.md, examples.md) ā add link + description ā confirm.
Option 5: Prompt for skill name ā create skill directory + SKILL.md ā create reference files with this solution ā confirm.
Option 6: Display created doc ā present menu again.
Option 7: Ask what they'd like to do.
/clavain:compound, manual trigger, confirmation phrase detectiondocs/solutions/[category]/[filename].mdschema.yaml exactly| Error | Action |
|---|---|
| Missing context | Ask user, don't proceed until critical info provided |
| YAML validation failure | Show specific errors, BLOCK until valid |
| Similar issue ambiguity | Present matches, let user choose |
| Module not in docs | Warn but don't block; suggest adding |
Good: exact error messages, file:line refs, observable symptoms, failed attempts, technical explanation (why not just what), code examples, prevention guidance, cross-references.
Bad: vague descriptions, missing technical details, no version/file context, unexplained code dumps, no prevention, no cross-references.