create-tooluniverse-skill

mims-harvard/tooluniverse · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/mims-harvard/tooluniverse --skill create-tooluniverse-skill
0 commentsdiscussion
summary

Systematic workflow for creating production-ready ToolUniverse skills.

skill.md

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
how to use create-tooluniverse-skill

How to use create-tooluniverse-skill on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add create-tooluniverse-skill
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/mims-harvard/tooluniverse --skill create-tooluniverse-skill

The skills CLI fetches create-tooluniverse-skill from GitHub repository mims-harvard/tooluniverse and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/create-tooluniverse-skill

Reload or restart Cursor to activate create-tooluniverse-skill. Access the skill through slash commands (e.g., /create-tooluniverse-skill) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.855 reviews
  • Aarav Nasser· Dec 28, 2024

    create-tooluniverse-skill has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Shikha Mishra· Dec 20, 2024

    Keeps context tight: create-tooluniverse-skill is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Anika Yang· Dec 20, 2024

    Keeps context tight: create-tooluniverse-skill is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Chinedu Mensah· Dec 16, 2024

    create-tooluniverse-skill reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Aarav Liu· Dec 16, 2024

    I recommend create-tooluniverse-skill for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Harper Abbas· Dec 8, 2024

    create-tooluniverse-skill fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Chen Sethi· Nov 23, 2024

    create-tooluniverse-skill fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Sakshi Patil· Nov 19, 2024

    We added create-tooluniverse-skill from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Aarav Chen· Nov 19, 2024

    Useful defaults in create-tooluniverse-skill — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Yash Thakker· Nov 11, 2024

    Registry listing for create-tooluniverse-skill matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 55

1 / 6