Loading...
Loading...
Found 3,152 Skills
Command a Royal Navy agent squadron from sailing orders through execution and stand-down. Use when work can be parallelized, requires tight coordination, or needs explicit action-station controls, quality gates, and a final captain's log.
This skill should be used when the user asks about Railway features, how Railway works, or shares a docs.railway.com URL. Fetches up-to-date Railway docs to answer accurately.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Clerk backend REST API
Create or update skills by generating, editing, or refining SKILL.md files in this repository. Use when authoring new skills or revising the structure, frontmatter, or guidance for existing ones.
Write a TECH.md spec for a significant Warp feature after researching the current codebase and implementation constraints. Use when the user asks for a technical spec, implementation plan, or architecture doc tied to a product spec.
Write a PRODUCT.md spec for a significant user-facing feature in Warp, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.
Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), for research papers and journal submissions.
Turn OSINT findings into a defensible intelligence product — BLUF key judgements, standardised estimative probability language, per-claim sourcing with timestamps and archived copies, separated observation/inference/assessment, documented negative findings and gaps, chain of custody and hashing, and redaction of uninvolved parties. Use for writing an OSINT report, intelligence brief, due-diligence memo, evidence pack, or executive summary of an investigation.
Query and propose local knowledge cards for this repo. Always use at the start of work here — run `npx knowcards query` before acting. Also use when wrapping up after proving a durable nuance, guideline, domain learning, or do/don't (propose a card). Skip only for routine edits in code you already hold with no repo nuance at stake, or if you already queried this topic in the session.
Use when rewriting rules without meaning loss.
Initialize and manage the evidence collection directory for professional security audits with documented proof of findings.