Loading...
Loading...
Found 16 Skills
Create Product Requirements Documents (PRD) following SDD methodology - Layer 2 artifact defining product features and user needs
Automatically discover life science APIs online, create ToolUniverse tools, validate them, and prepare integration PRs. Performs gap analysis to identify missing tool categories, web searches for APIs, automated tool creation using devtu-create-tool patterns, validation with devtu-fix-tool, and git workflow management. Use when expanding ToolUniverse coverage, adding new API integrations, or systematically discovering scientific resources.
Toolkit for creating and validating skills and subagents. Use when: creating a new skill (fast or full mode), validating an existing skill, deciding Skills vs Subagents, migrating docs to skills, estimating token cost, or running a security scan. Triggers: "create skill", "build skill", "validate skill", "new subagent", "skills vs subagents", "estimate tokens", "security scan".
Used for header-only preflight of one DICOM series folder before conversion or inference. Not for de-identification or clinical clearance.
Automated jaan-to release preparation with validation, docs sync, version bump, and PR creation
[Hyper] Create and refactor AI-readable docs, instruction bases, runbooks, specs, and harness-ready rule packs for context, prompt, tool, eval, sourcing, safety, and validation workflows.
Create Architecture Decision Records (ADR) - Layer 5 artifact documenting architectural decisions with Context-Decision-Consequences format
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.
Use when building joi schemas, custom validators, extensions, or working with joi's validation pipeline. Covers all types, references, templates, errors, and the extension API.
Optimize agent skills to reduce context bloat while preserving answer coverage. Use when: (1) A skill's SKILL.md body exceeds ~250 lines or duplicates its references/ files (2) A skill's YAML description is verbose or triggers false positives from sibling skills (3) Planning or executing a body/reference split for a skill (4) Auditing skill token efficiency
Design Solana/Anchor instructions with clear inputs, constraints, authority checks, and invariants. Use when defining or reviewing instruction APIs.
Validation stage for the cli-forge skill family: run the documented compliance checks for an existing project and report whether it is planning-brief-compliant, usable with warnings, or blocked by errors.