Loading...
Loading...
Found 94 Skills
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity compliance", "filing deadlines", "annual reports due", "entity tracker", "what filings are due", "entity health", or "good standing".
Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
Gate every generation through a brand policy file.
Generates and reviews test scenarios based on IPA non-functional grade standards. Analyzes system requirements to identify critical test viewpoints for performance, security, and availability.
Automatically generate product documentation that complies with Doom framework specifications, supporting PRD transformation, architectural analysis, and multi-type document generation.
Novel outline/worldview/character design, applicable to user requests such as "Help me write a novel outline", "Design the protagonist's character", "Create a worldview setting", "Build a novel plot framework", "Write volume-specific detailed outlines", "Design novel characters for me", "Create a fantasy worldview", "Help me sort out the novel plot", "Novel character setting", "Write chapter-by-chapter outlines for novels", "Plan the arrangement of cool points", "Create novel character cards", "Build a novel world", etc. It generates complete worldviews, character cards, plot outlines, and cool point plans, with automatic compliance checks to avoid infringement risks. **When generating a large number of chapter detailed outlines, sub-Agents are used for parallel processing, and each Agent is responsible for at most 3 chapters' detailed outlines**
Designs and documents structured incident response playbooks that define step-by-step procedures for specific incident types aligned with NIST SP 800-61r3 and SANS PICERL frameworks. Covers playbook structure, decision trees, escalation criteria, RACI matrices, and integration with SOAR platforms. Activates for requests involving IR playbook creation, incident response procedure documentation, response runbook development, or SOAR playbook design.
Full-repo SAP Converged Cloud Go compliance audit. Reviews every package against established review standards — focusing on over-engineering, error message quality, dead code, interface contracts, copy-paste structs, and pattern consistency with keppel. Dispatches parallel agents by package group, each reading ALL sapcc rules. Produces code-level findings with actual before/after diffs. Invoked via "/sapcc-audit" or through /do.
Test APIs against OWASP API Security Top 10 including discovery, auth abuse, and protocol-specific checks.
You MUST use this when writing or editing prose anywhere in a project (docs, READMEs, comments, commit messages, UI copy) and when asked to audit, score, or clean up dash usage. It bans typographic dashes (em and en) in favor of the plain hyphen and grades a project's compliance on a 0-100 scale.