Your agent can do more. Find the skill that makes it happen.
Find your next superpower If you are an agent, refer to our llms.txt for full access.Use when a user explicitly asks for a committee or subagents to iteratively review, score, and revise an output until a calibrated target such as 10/10 is reached with evidence.
The single communication rule for every reply. Mandatory four-part status (asked, done, state, next); settle scope first, then execute the whole task in one pass without asking, including same-pass doc obligations and self-correction; hard stops only for outward, destructive or scope-creep actions; report every change made; interrupt-and-resume; plain technical writing register, tone and formatting. Use on every conversation turn.
Supports singular and plural alternative pages, your product versus a competitor, and comparisons between competitors. Emphasizes deep research, modular content structure, and varied sections beyond feature tables.
Compiles a temporary AL project through the workflow-installed public prerelease ALTool and verifies that a fresh app package was emitted.
Full ASVS 5.0 compliance assessment against a codebase and/or architecture diagrams. Reads all 346 controls from the companion CSV, performs targeted code analysis per control, and produces a complete matrix marked COMPLIANT / NON_COMPLIANT / NOT_RELEVANT — with per-control reasoning and evidence (code snippets, file:line references, diagram observations). Outputs a reviewed CSV matrix and a self-…
Unified compliance verification across ISO 27001, NIST CSF, CIS Controls, NIS2, EU CRA, GDPR, SOC 2, PCI DSS, and HIPAA for cybersecurity consulting
Cross-framework compliance alignment and control mapping between ISO 27001, NIST CSF, CIS Controls, and GDPR
Multi-framework compliance (ISO 27001, NIST CSF, CIS Controls, GDPR, NIS2, EU CRA, SOC 2), control mapping
Passively analyzes workflows for repetitive patterns and opportunities to create EPCI components. Identifies candidates for skills, commands, or subagents without actively creating them.
Use when creating, naming, or placing a file or folder in libs/, or when modifying or adding a file to an existing component (even when the barrel isn't touched) — component vs utility naming, the one-responsibility-per-file layout, when a folder needs an index.ts barrel (public API only), and the required set of files a component needs per lib. Load this before scaffolding or restructuring a c…
Use when designing or changing a component's public API, its composition, or its state model in libs/ui-react or libs/ui-rnative — layering (core vs internal vs primitives), BaseProps/Props splits, converting a component to compound / changing its composition with createSafeContext, controlled/uncontrolled state, prop-naming conventions, and cross-platform API parity. Load this before shaping a ne…
Use when writing or editing Storybook MDX docs (.mdx) — the two-tab Overview/Implementation structure, story-backed <Source> examples, and doc table guidelines.
Skills give your agent reusable instructions for a specific job. Pick one, read what it does, and bring it into your workflow.
A name only tells half the story. Search the full description and instructions to find the right fit.
Read the skill, visit its source, and see exactly what you’re adding to your agent.
Copy the install command from a skill page and run it in your project.
npx skillycli add owner/repo --skill name