984 skills · sorted by relevance
Turn cryptographic code or specifications into sequence diagrams showing who sends each message, which cryptographic operations occur, and where failures stop the exchange. Outputs include Mermaid source, a plain text diagram, and a protocol summary.
Compare implementation code with a specification, whitepaper, or design document. It checks individual requirements, independently challenges reported mismatches, and writes evidence-based reports covering missing or partial implementation, contradictions, undocumented behavior, and requirements that cannot be judged.
Review smart contract projects against Trail of Bits development guidelines. Examines architecture, upgrade mechanisms, implementation, dependencies, and tests, then provides system documentation, identifies gaps, and recommends improvements in priority order with code references.
Inspect DWARF, the debug information stored with compiled code, to find functions and types, check structural integrity, and clarify specification details. Also helps write parsing tools using libraries such as pyelftools, libdwarf, or gimli.
Plan and implement features with a workflow that adapts to their complexity. It connects testable requirements to tasks, tests, and small commits, then checks the finished work against the specification through an independent verification pass.
Turn an agreed specification or ticket into a checklist with specific tests or commands for each requirement. Implement the work, run the checks, and have a separate agent verify the entire feature.
Coauthor proposals, specifications, and other structured documents through context gathering, section-by-section drafting, and revision. Test the finished draft with a fresh Claude conversation to identify unclear assumptions, missing information, and contradictions.
Clean up DeepChat's specification-driven development documents after implementation and validation. Review feature, issue, and architecture files, remove completed or obsolete material when evidence supports deletion, and preserve maintained specifications while checking references.
Execute an existing Ouroboros Seed, a specification containing a goal and acceptance criteria, as a background job. The workflow checks each criterion, normally queues formal evaluation, and follows a bounded improvement loop if evaluation rejects the result.
Learn Ouroboros through a short, hands-on interview about your own project idea. Turn your answers into a sample specification with goals, constraints, and checkable outcomes, then learn the commands for execution, evaluation, and next steps.
Run repeated Ouroboros execution and improvement cycles as a background job, starting from a Seed specification or continuing an existing lineage. The loop stops on a quality check pass, convergence, cancellation, or the generation limit, and reports the outcome.
Extract details from an open eBay listing into JSON, a structured data format. Collect prices, availability, sales counts, seller feedback, specifications, and image links for product comparisons and catalog checks across regional eBay sites.
Extract structured product records from Amazon URLs across regional sites, including price, stock, specifications, rating breakdowns, sellers, and visible variants. Use the records for competitor research, catalog audits, or tracking product prices and availability.
Develop and fix Nexent features by connecting written specifications, acceptance criteria, implementation, and verification evidence. Plan unit tests and appropriate staged checks, maintain their links to requirements, and fill confirmed test gaps after development.
Learn the complete OpenSpec workflow through a small task in an actual codebase. The agent explains each stage while creating a proposal, specifications, design, and tasks, then implements the change and archives its records.
Co-write proposals, technical specifications, and decision documents through context gathering, section-by-section drafting, and revision. A fresh AI reader then tests the document to reveal unclear explanations, missing context, and contradictions before it is shared.
Investigate exposed source maps, configuration files, Git history, and API specifications on websites. The skill guides source reconstruction and artifact inspection to identify leaked secrets, internal routes, and build details during the initial stages of security research.
Inventory old and undocumented API versions, then compare their authentication, request limits, input validation, and exposed fields with current versions. Uses API specifications and archived records to identify overlooked endpoints with weaker security controls.
Review API configuration and input handling for unauthorized field updates, prototype pollution that alters shared object defaults, and manipulation of backend URLs. The skill also covers exposed API specifications and access control weaknesses in OData queries.
Find the right skill and sequence for your current development task, from shaping an idea to implementation, debugging, and review. The guide also explains when to prototype, prepare specifications, or move work into a fresh session.
Implement work described in a specification or set of tickets, using test-first development where agreed. Run type checks and tests throughout, review the completed changes, and commit the work to the current branch.
Turn a specification and its linked tickets into code. Multiple agents work on available tasks in separate worktrees, combine changes on one integration branch, and complete a code review before preparing the result for review or closing tickets.
Turn plans, specifications, or conversations into small implementation tickets that each deliver verifiable behavior. Define acceptance criteria and dependencies, review the breakdown together, then publish approved tickets to the configured tracker or local Markdown files.
Develop a research idea through a structured conversation, then turn the answers into a written research specification. Clarify the question, testable hypothesis, data needs, methods for assessing cause and effect, expected findings, and feasibility.