2.4K skills · sorted by relevance
Turn a development phase into an actionable PLAN.md through research, planning, and verification. The skill can incorporate requirements or recorded design decisions, then check and revise the plan before presenting the results.
Audit a development milestone before archiving it by checking requirements, connections between phases, and complete user flows. It reads existing verification reports and gathers technical debt and deferred gaps to assess whether the original completion criteria were met.
Extract decisions, lessons, recurring patterns, and unexpected findings from the artifacts of a completed development phase. It organizes these learnings into a LEARNINGS.md file using planning, summary, verification, acceptance testing, and state documents.
Guide a development team from an assigned user outcome through implementation, testing, and handoff. It covers reproducing defects, checking behavior against requirements, involving design when needed, and reporting the exact changes, verification results, and remaining uncertainty.
Design tests for charts, dashboards, and interactive diagrams. Combine data checks, component tests, screenshot comparisons, and end-to-end workflows to catch incorrect values, broken interactions, and visual changes while keeping tests stable.
Design workflows for completing business lead records, verifying contact details, and ranking prospects against an ideal customer profile. Plan provider sequences in Clay, scoring rules, and data quality checks around lead volume, existing tools, and budget.
Guide feature development from a human-reviewed plan to testable requirements, implementation, and independent verification. Record each requirement with a concrete proof, then have a separate agent check the work and produce a verification report.
Organize substantial tasks into a cycle of creation, independent review, and revision while preserving the original request. Turn broad quality goals into observable checks, collect evidence, and finish with verified results or a clearly identified blocker.
Look up a company's Trustpilot profile using its domain to collect ratings, review counts, verification status, and contact details. Optional metrics show how the business responds to negative reviews, supporting company comparisons and reputation research.
Retrieve Instagram profile details from a username, including the bio, follower and following counts, post count, verification status, and external link. Use the collected information to review an account’s profile and audience size.
Check background type checks, tests, and builds in a Git worktree, a separate working directory. Read verification logs to see results, failure counts, and errors, with suggested next actions while development continues.
Checks code changes before a pull request by reviewing builds, types, coding rules, tests, potential secrets, and changed files. Produces a report showing results, test coverage, and issues that need fixing.
Delegate a focused coding, research, review, or verification task to a separate DevSpace agent. Choose an available worker, provide a self-contained brief, inspect or wait for results, and continue related work with the same agent.
Create a project-specific SKILL.md that teaches an agent how to launch, operate, and verify an app. It tests a representative workflow first, then records reliable steps, evidence of success, cleanup instructions, and maintenance guidance.
Checks code changes before a pull request by reviewing builds, types, coding rules, tests, potential secrets, and changed files. Produces a report showing results, test coverage, and issues that need fixing.
Check an academic paper’s tables, numerical claims, and modeling choices against R scripts and outputs. Produce discrepancy reports, a record linking claims to code, and automated tests that rerun the analysis.
Coordinate research, drafting, citation and data verification, AI review, revision, and final formatting through connected skills. Start from a research topic, an existing manuscript, or reviewer comments, with progress tracking and user checkpoints.
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
The English summary is being prepared. Showing the original description.
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
The English summary is being prepared. Showing the original description.
[omh] Proof a change is done before merge: define and record build, lint, typecheck, test, security, docs, generated-output, and CI evidence before completion or merge. Use when the user says: verification-gate, verification gate, quality gate, release gate, test gate, build lint test, lint typecheck tests, verify before merge.
The English summary is being prepared. Showing the original description.
Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, "model-check this race", "prove this invariant", or when concurrency, retries, state machines, parsers, or unsafe code need more than tests.
The English summary is being prepared. Showing the original description.
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
The English summary is being prepared. Showing the original description.
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", "make a driver skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
The English summary is being prepared. Showing the original description.
Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in any language, with whichever verification tool fits. Use for /create-formal-verification-skill, "model-check this race", "prove this invariant", or when concurrency, retries, state machines, parsers, or unsafe code need more than tests.
The English summary is being prepared. Showing the original description.