This repo contains reusable RaidGuild agent skills. Treat it as a maintainability project first and a skill-writing project second.
- Do not create a new skill for a one-off campaign, persona, client, channel, or workflow.
- Create a new skill only when it owns a durable capability that will be reused across tasks.
- Put exported Prism skill source material under
references/prism-skills/<skill-name>/SKILL.md. - Put exported Prism workflow source material under
references/prism-workflows/<workflow-key>/. - Put analysis, inventories, and migration notes under
references/prism-skills/. - Add to
skills/only when a candidate skill has a clear boundary, migration source, and validation path. - Do not commit secrets, tokens, internal URLs, client-private details, wallet keys, private operational notes, or environment-specific paths.
- Prefer concise
SKILL.mdfiles with deeper material in localreferences/files. - Use cross-references instead of copying rules between skills.
Before adding a skill, answer:
- What durable capability does this skill own?
- Which existing Prism skills does it absorb or supersede?
- Which rules belong in shared safety, brand, research, or publishing skills instead?
- What references should be loaded only on demand?
- How will the skill be validated on a realistic task?
If those answers are unclear, keep the work in references/prism-skills/ until the boundary is clearer.
skills/: only refactored and validated skills.references/prism-skills/<skill-name>/SKILL.md: exported Prism custom skill reference copies.references/prism-workflows/<workflow-key>/: exported Prism workflow reference copies.references/prism-skills/inventory.md: structured list of current Prism skills and migration decisions.references/prism-skills/refactor-notes.md: observations, grouping ideas, and open questions.docs/: repo-level architecture and process docs.