Loading...
Loading...
Found 986 Skills
Impact Analysis Helper - Auto-activating skill for Enterprise Workflows. Triggers on: impact analysis helper, impact analysis helper Part of the Enterprise Workflows skill category.
Automatically generate product documentation that complies with Doom framework specifications, supporting PRD transformation, architectural analysis, and multi-type document generation.
Github Issue Creator - Auto-activating skill for Enterprise Workflows. Triggers on: github issue creator, github issue creator Part of the Enterprise Workflows skill category.
Use to identify, score, and prioritize customer advocates for programs.
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.
Gate every generation through a brand policy file.
When the user wants to build or improve a sales bot's ability to avoid making claims that create liability. Also use when the user mentions "compliance," "legal risk," "claim avoidance," "regulated industries," or "liability prevention."
Advisory fee billing: fee calculation (tiered, flat, breakpoint), billing cycles, AUM valuation, direct-debit/invoice collection, GAAP revenue recognition, ADV Part 2A/Reg BI/ERISA 408(b)(2) disclosure, billing exceptions, system migration, revenue forecasting, concentration analysis.
/cs:gc-review <plan> — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface.
Test APIs against OWASP API Security Top 10 including discovery, auth abuse, and protocol-specific checks.
When the user wants to build or improve a sales bot's ability to orchestrate SMS, email, voice, and chat without overwhelming prospects. Also use when the user mentions "omnichannel," "cross-channel," "channel orchestration," "multi-touch sequences," or "coordinating outreach."
Legacy-project style inheritance skill. Use when the user types /inherit-legacy-style, or when onboarding an AI coding agent onto a hand-written legacy project and you need to prevent "style drift" (the model imposing its pretrained mainstream idioms onto the project). Language- and framework-agnostic — it aligns meta-architecture only, not syntax. Once run, it becomes a behavioral constraint on all subsequent coding tasks. Do NOT use for pure research or one-off questions unrelated to code-style alignment.