---

name: meta-tools description: Meta-tools is a comprehensive framework for creating, validating, optimizing, and composing development tools. It provides automated workflows for tool generation, cross-tool composition, and orchestration patterns that enable developers to build custom tooling ecosystems. version: 1.0.0 category: foundry tags:

• foundry
• creation
• meta-tools author: ruv

---

<!-- SKILL SOP IMPROVEMENT v1.0 -->

Skill Execution Criteria

When to Use This Skill

• [AUTO-EXTRACTED from skill description and content]
• [Task patterns this skill is optimized for]
• [Workflow contexts where this skill excels]

When NOT to Use This Skill

• [Situations where alternative skills are better suited]
• [Anti-patterns that indicate wrong skill choice]
• [Edge cases this skill doesn't handle well]

Success Criteria

• primary_outcome: "[SKILL-SPECIFIC measurable result based on skill purpose]"
• quality_threshold: 0.85
• verification_method: "[How to validate skill executed correctly and produced expected outcome]"

Edge Cases

• case: "Ambiguous or incomplete input" handling: "Request clarification, document assumptions, proceed with explicit constraints"
• case: "Conflicting requirements or constraints" handling: "Surface conflict to user, propose resolution options, document trade-offs"
• case: "Insufficient context for quality execution" handling: "Flag missing information, provide template for needed context, proceed with documented limitations"

Skill Guardrails

NEVER:

• "[SKILL-SPECIFIC anti-pattern that breaks methodology]"
• "[Common mistake that degrades output quality]"
• "[Shortcut that compromises skill effectiveness]" ALWAYS:
• "[SKILL-SPECIFIC requirement for successful execution]"
• "[Critical step that must not be skipped]"
• "[Quality check that ensures reliable output]"

Evidence-Based Execution

self_consistency: "After completing this skill, verify output quality by [SKILL-SPECIFIC validation approach]" program_of_thought: "Decompose this skill execution into: [SKILL-SPECIFIC sequential steps]" plan_and_solve: "Plan: [SKILL-SPECIFIC planning phase] -> Execute: [SKILL-SPECIFIC execution phase] -> Verify: [SKILL-SPECIFIC verification phase]"

<!-- END SKILL SOP IMPROVEMENT -->

Meta-Tools - Tool Creation and Composition Framework

Overview

Meta-tools is a comprehensive framework for creating, validating, optimizing, and composing development tools. It provides automated workflows for tool generation, cross-tool composition, and orchestration patterns that enable developers to build custom tooling ecosystems.

Purpose

Enable developers to:

• Generate Tools: Automatically create new tools from specifications
• Validate Tools: Ensure tool correctness, security, and performance
• Optimize Tools: Enhance tool efficiency and resource usage
• Package Tools: Bundle tools for distribution and deployment
• Compose Tools: Chain multiple tools into powerful workflows
• Orchestrate Tools: Coordinate complex multi-tool operations

Capabilities

Tool Generation

• Specification-driven tool creation
• Template-based scaffolding
• Auto-generated validation logic
• Built-in error handling
• Documentation generation

Tool Validation

• Schema validation
• Security scanning
• Performance profiling
• Integration testing
• Compliance checking

Tool Optimization

• Performance analysis
• Resource optimization
• Caching strategies
• Parallel execution
• Memory management

Tool Packaging

• Dependency resolution
• Version management
• Distribution packaging
• Installation scripts
• Update mechanisms

Tool Composition

• Pipeline creation
• Data flow management
• Error propagation
• State management
• Result aggregation

Tool Orchestration

• Multi-tool coordination
• Parallel execution
• Conditional workflows
• Event-driven triggers
• Monitoring and logging

Usage Patterns

Quick Tool Generation

# Generate a new tool from specification
python resources/tool-generator.py \
  --spec specs/my-tool.yaml \
  --output tools/my-tool \
  --template resources/templates/tool-template.yaml

Tool Validation

# Validate a tool implementation
node resources/tool-validator.js \
  --tool tools/my-tool \
  --checks security,performance,integration

Tool Optimization

# Optimize tool performance
bash resources/tool-optimizer.sh \
  --tool tools/my-tool \
  --profile production \
  --optimize memory,speed

Tool Packaging

# Package tool for distribution
python resources/tool-packager.py \
  --tool tools/my-tool \
  --format npm,docker \
  --output dist/

Tool Composition

// Compose multiple tools into a workflow
const { ComposeTool } = require('./examples/tool-composition');

const workflow = new ComposeTool([
  { name: 'validator', config: {...} },
  { name: 'transformer', config: {...} },
  { name: 'optimizer', config: {...} }
]);

await workflow.execute(input);

Tool Orchestration

// Orchestrate complex multi-tool operations
const { OrchestrateTool } = require('./examples/tool-orchestration');

const orchestrator = new OrchestrateTool({
  tools: [...],
  strategy: 'parallel',
  errorHandling: 'continue'
});

await orchestrator.run();

Architecture

Components

1. Tool Generator: Creates tools from specifications
2. Tool Validator: Validates tool correctness and security
3. Tool Optimizer: Enhances tool performance
4. Tool Packager: Bundles tools for distribution
5. Composition Engine: Chains tools into workflows
6. Orchestration Engine: Coordinates multi-tool operations

Templates

• tool-template.yaml: Base tool structure
• meta-config.json: Framework configuration
• tool-manifest.yaml: Tool metadata and dependencies

Workflow

Specification → Generation → Validation → Optimization → Packaging → Distribution
                                ↓
                           Composition → Orchestration → Execution

Integration

With Existing Tools

• Import existing tools via adapters
• Wrap legacy tools with modern interfaces
• Bridge different tool ecosystems
• Provide unified API layer

With CI/CD

• Automated tool generation in pipelines
• Continuous validation and testing
• Performance regression detection
• Automated packaging and deployment

With Monitoring

• Tool execution metrics
• Performance tracking
• Error rate monitoring
• Resource usage analysis

Best Practices

Tool Design

• Keep tools focused on single responsibility
• Use clear, consistent interfaces
• Provide comprehensive error messages
• Include detailed documentation
• Support configuration externalization

Composition

• Design for composability from the start
• Use standard data formats between tools
• Handle errors gracefully
• Implement proper cleanup
• Support transaction-like behavior

Orchestration

• Plan for parallel execution
• Implement proper synchronization
• Handle partial failures
• Provide rollback mechanisms
• Log all operations

Sub-Skills

This meta-tools framework includes specialized sub-skills:

1. Skill Gap Analyzer - Identifies missing capabilities and suggests tools
2. Token Budget Advisor - Optimizes tool usage within constraints
3. Prompt Optimization Analyzer - Enhances tool prompts and interactions

Examples

See the examples/ directory for comprehensive demonstrations:

• create-tool.js - Complete tool creation workflow
• tool-composition.js - Multi-tool composition patterns
• tool-orchestration.js - Complex orchestration scenarios

Testing

Run the test suite:

npm test                    # Run all tests
npm test validator          # Test validation logic
npm test composer           # Test composition engine
npm test orchestrator       # Test orchestration engine

Performance

• Tool Generation: < 1 second for standard tools
• Validation: < 5 seconds for comprehensive checks
• Optimization: 20-40% performance improvement typical
• Composition: Near-zero overhead for chaining
• Orchestration: Efficient parallel execution with resource pooling

Security

• Input sanitization in all tools
• Sandboxed execution environments
• Dependency vulnerability scanning
• Access control and permissions
• Audit logging for all operations

Support

For issues, questions, or contributions:

• Check the documentation in README.md
• Review examples in examples/
• Run tests in tests/
• Consult sub-skill documentation

License

Part of the SPARC Three-Loop System