511 skills · sorted by relevance
Turn specifications or requirements into an implementation plan before coding begins. Break work into testable tasks with exact files, function definitions, test assertions, and verification commands, so another developer or agent can follow the plan.
Turn recurring work or life activities into workflow specifications through focused questions with recommended answers. Clarify triggers, human review, and decision summaries so an implementation agent can build the workflow without further questions.
Co-write proposals, specifications, and decision documents through a guided process. Gather background, draft and refine each section, then test the document with a fresh Claude conversation to find unclear explanations and missing context.
Turn specifications into pseudocode, a language-independent outline of program logic. Define data structures, handle edge cases, analyze time and memory requirements, and document design patterns and optimization opportunities before implementation.
Turn specifications and algorithm outlines into a system architecture. Define components, interfaces, data structures, and deployment plans, then document technology choices, security measures, failure handling, and plans for supporting increased usage.
Turn specifications and designs into working code using test-driven development: write failing tests, implement enough code to pass, then refactor. The workflow also covers error handling, performance improvements, documentation, and coordinated changes across components.
Carry out Docupost tasks through Rube MCP, an agent connection to external tools. Discover supported actions, check their required inputs and the service connection, then execute operations according to the specifications returned by tool search.
Update main OpenSpec specifications from a change's delta specs, which describe specification changes. The skill merges requirement additions, edits, removals, and renames while preserving unrelated content, validates the results, and leaves the change active.
Compare an implementation with its OpenSpec specifications, tasks, and design decisions before archiving the change. Get a report on completion, requirement coverage, and consistency, with prioritized issues, actionable recommendations, and explicit limits where evidence is missing.
Plan the visual and narrative direction of HyperFrames videos, including colors, fonts, composition, narration, and scene rhythm. The skill helps apply existing design specifications, choose a style, and check whether the finished work follows that direction.
Turn a math or science video idea into a detailed scene plan. Research the topic, clarify the audience, and outline visuals, narration, transitions, and implementation notes for Manim, an animation tool.
Create HeyGen avatar videos with a chosen presenter, voice, exact script, and backgrounds for each scene. Use photos as presenters, generate transparent WebM files for compositing, or produce batches of videos with consistent specifications.
Consult Sally, a UX and UI specialist, to translate user needs into interaction designs and UX specifications. The role considers unusual situations as well as everyday use, helping communicate clear design intent to architecture and implementation work.
Record durable Cherry Studio engineering decisions in Agent Notes. Determine which changes need a note, prepare specifications with verifiable acceptance criteria, and manage approval, implementation, rejection, and replacement while preserving the reasoning behind decisions.
Assess Airflow Improvement Proposals by comparing Confluence specifications with pull requests, commits, and codebase files. Produce evidence-backed progress reports showing delivered items, remaining work, and specification updates needed across one or more proposals.
Generate API documentation from source code, including OpenAPI/Swagger specifications. Describe endpoints, the addresses used to access API operations, with parameters, responses, errors, authentication guidance, and examples in cURL, JavaScript, and Python.
Create or update API documentation from source code. The skill produces OpenAPI/Swagger specifications, descriptions of API operations, parameter and response references, authentication guidance, and practical examples for developers integrating an API.
Organize features, bug fixes, and refactors as Conductor tracks, units of related work. Create specifications and task plans, maintain status and dependency records, and preserve completed work with verification details and commit references.
Design and review REST and GraphQL APIs with consistent naming, data structures, error responses, pagination for large result sets, and versioning strategies. Helps teams define shared standards and plan changes that existing clients can adopt gradually.
Research products against a budget and required features, then compare prices, specifications, and review findings in a table. Get one recommendation with its tradeoff, plus a price history check for deals when available.
Compare project documentation with existing code to identify missing core features. Rank the gaps and create GitHub issues with practical specifications, implementation plans, acceptance criteria, effort estimates, and dependencies.
Create structured Markdown specifications that AI agents can read and use. Organize requirements, constraints, interfaces, acceptance criteria, and testing plans into a self-contained document with clear definitions and examples.
Build an llms.txt file, a navigation guide for AI models, from a repository's structure. Summarize the project and organize links to essential documentation, specifications, examples, and configuration resources.
Write or revise instructions, specifications, tickets, and skill files so an agent can act without prior chat history. Make rules checkable, explain their reasons, define completion criteria, and keep authoritative information in one place.