verify-openspec-docs
Uses a fresh-context subagent to verify documentation claims against source and rerun documented commands. Manually checks pages, sections, or changed claims independently of the drafting loop.
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.Uses a fresh-context subagent to verify documentation claims against source and rerun documented commands. Manually checks pages, sections, or changed claims independently of the drafting loop.
Verifies that the workflow-installed public prerelease ALTool is the executable used for every reproduction command.
Checks a stage's diff before completion to verify new entities, services, resource templates, and enum values reach all relevant downstream registries. Covers database models, RLS membership and migrations, dependency injection, query-filter allow-lists, localization pairs, and audit-log tests.
Restates a claim in falsifiable terms, captures baseline and treatment evidence, and compares artifacts. Returns VERIFIED, NOT VERIFIED, or INCONCLUSIVE.
Defines completion through exercising changes at their user-facing or operational surface and running verification commands. Requires faithful outcome reporting, attention beyond passing suites, and ownership of failing verification gates.
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. Ends with the agent running npm publish itself using the maintainer's npm token.
Establishes version control practices for design assets, components, and libraries. Covers branching, naming, and releases to organize file history.
Guides the version release process and GitHub Release notes. Excludes documentation and changelog pages.
Covers feature folders, endpoint grouping, and handler patterns using Mediator, Wolverine, or plain handler classes. Supports work in existing VSA projects and adding new feature slices.
Creates cursor light trails, chromatic rays, and directional flares. These effects support word-by-word quote reveals in video intros.
How to use @owlmeans/viable-common — the runtime-free contract package of the OwlMeans Viable platform. Covers planning cards and flows (including the landing-gate and tenancy fields), project/story refusals, slot commands and layouts, slot metadata keys, target integrity, connector domain statuses and routes, the intent-first hand-off (`./intent`), shared legal dates (`./legal`), conversion vocabulary, blueprint layer types and case vocabulary, ViableSkill/ViablePersona nam…
Runs Mistral Vibe CLI (vibe) as a background implementer for coding tasks or queues. The delegating agent reviews the produced diff and integrates the result.
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