create-tooluniverse-skill
Create high-quality ToolUniverse skills following test-driven, implementation-agnostic methodology.
What this skill does
# Create ToolUniverse Skill Systematic workflow for creating production-ready ToolUniverse skills. ## Core Principles Build on the 10 pillars from `devtu-optimize-skills`: 1. TEST FIRST - never document untested tools 2. Verify tool contracts - don't trust function names 3. Handle SOAP tools - add `operation` parameter 4. Implementation-agnostic docs - no Python/MCP code in SKILL.md 5. Foundation first - query aggregators before specialized tools 6. Disambiguate carefully - resolve IDs properly 7. Implement fallbacks - Primary -> Fallback -> Default 8. Grade evidence - T1-T4 tiers on claims 9. Quantified completeness - numeric minimums per section 10. Synthesize - models and hypotheses, not just lists See `OPTIMIZE_INTEGRATION.md` for detailed application of each pillar. ## 7-Phase Workflow | Phase | Duration | Description | |-------|----------|-------------| | 1. Domain Analysis | 15 min | Understand use cases, data types, analysis phases | | 2. Tool Discovery | 30-45 min | Search, read configs, test tools (MANDATORY) | | 3. Tool Creation | 0-60 min | Create missing tools via devtu-create-tool | | 4. Implementation | 30-45 min | Write python_implementation.py with tested tools | | 5. Documentation | 30-45 min | Write SKILL.md (agnostic) + QUICK_START.md | | 6. Validation | 15-30 min | Run test suite, validate checklist, manual verify | | 7. Packaging | 15 min | Create summary, update tracking | **Total**: ~1.5-2 hours (without tool creation). ### Phase 1: Domain Analysis - Gather concrete use cases and expected outputs - Identify inputs, outputs, and intermediate data types - Break workflow into logical phases - Review existing skills in `skills/` for patterns ### Phase 2: Tool Discovery and Testing Search tools in `/src/tooluniverse/data/*.json` (186 tool files). For each tool, read its config to understand parameters and return schema. See `PARAMETER_VERIFICATION.md` for common pitfalls. **Create and run a test script** using `test_tools_template.py`. For each tool: call with known-good params, verify response format, document corrections. See `TESTING_GUIDE.md` for the full test suite template and procedures. ### Phase 3: Tool Creation (If Needed) Invoke `devtu-create-tool` when required functionality is missing and analysis is blocked. Use `devtu-fix-tool` if new tools fail tests. ### Phase 4: Implementation Create `skills/tooluniverse-[domain]/` with: - `python_implementation.py` - use only tested tools, try/except per phase, progressive report writing - `test_skill.py` - test each input type, combined inputs, error handling Use templates from `CODE_TEMPLATES.md`. ### Phase 5: Documentation Write implementation-agnostic SKILL.md using `SKILL_TEMPLATE.md`. Write multi-implementation QUICK_START.md using `QUICKSTART_TEMPLATE.md`. Key rules: zero Python/MCP code in SKILL.md, equal treatment of both interfaces in QUICK_START. See `IMPLEMENTATION_AGNOSTIC.md` for format guidelines with examples. ### Phase 6: Validation Run the comprehensive test suite (see `TESTING_GUIDE.md`). Validate against `VALIDATION_CHECKLIST.md`. Perform manual verification: load ToolUniverse fresh, copy-paste QUICK_START example, verify output works. ### Phase 7: Packaging Create summary document using `PACKAGING_TEMPLATE.md`. Update session tracking if creating multiple skills. ## Skill Integration | Skill | When to Use | |-------|-------------| | **devtu-create-tool** | Critical functionality missing | | **devtu-fix-tool** | Tool returns errors or unexpected format | | **devtu-optimize-skills** | Evidence grading, report optimization | ## Quality Indicators **High quality**: 100% test coverage before docs, agnostic SKILL.md, multi-implementation QUICK_START, fallback strategies, parameter corrections table, response format docs. **Red flags**: Docs before testing, Python in SKILL.md, assumed parameters, no fallbacks, SOAP tools missing `operation`, no test script. ## Reference Files | File | Content | |------|---------| | `SKILL_TEMPLATE.md` | Template for writing SKILL.md | | `QUICKSTART_TEMPLATE.md` | Template for writing QUICK_START.md | | `TESTING_GUIDE.md` | Test suite template and procedures | | `VALIDATION_CHECKLIST.md` | Pre-release quality checklist | | `PACKAGING_TEMPLATE.md` | Summary document template | | `PARAMETER_VERIFICATION.md` | Tool parameter verification guide | | `OPTIMIZE_INTEGRATION.md` | devtu-optimize-skills 10-pillar integration | | `IMPLEMENTATION_AGNOSTIC.md` | Implementation-agnostic format guide with examples | | `CODE_TEMPLATES.md` | Python implementation and test templates | | `test_tools_template.py` | Tool testing script template |
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.