DNYoussef

Meta-Tools - Tool Creation and Composition Framework

Context Cascade - Nested Plugin Architecture for Claude Code Official Claude Code Plugin | Version 3.1.0 | Last updated: 2026-01-09 (see docs/COMPONENT-COUNTS.json for source counts) Context-saving nested architecture: Playbooks -> Skills -> Agents -> Commands. Load only what you need, saving 90%+ context space.

DNYoussef 30 6 Updated 4mo ago

Resources

8
GitHub

Install

npx skillscat add dnyoussef/context-cascade/skills-foundry-meta-tools

Install via the SkillsCat registry.

SKILL.md

/============================================================================/
/* META-TOOLS SKILL :: VERILINGUA x VERIX EDITION /
/
============================================================================*/


name: meta-tools
version: 1.0.0
description: |
[assert|neutral] 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 orchestr [ground:given] [conf:0.95] [state:confirmed]
category: foundry
tags:

  • foundry
  • creation
  • meta-tools
    author: ruv
    cognitive_frame:
    primary: aspectual
    goal_analysis:
    first_order: "Execute meta-tools workflow"
    second_order: "Ensure quality and consistency"
    third_order: "Enable systematic foundry processes"

/----------------------------------------------------------------------------/
/* S0 META-IDENTITY /
/
----------------------------------------------------------------------------*/

[define|neutral] SKILL := {
name: "meta-tools",
category: "foundry",
version: "1.0.0",
layer: L1
} [ground:given] [conf:1.0] [state:confirmed]

/----------------------------------------------------------------------------/
/* S1 COGNITIVE FRAME /
/
----------------------------------------------------------------------------*/

[define|neutral] COGNITIVE_FRAME := {
frame: "Aspectual",
source: "Russian",
force: "Complete or ongoing?"
} [ground:cognitive-science] [conf:0.92] [state:confirmed]

Kanitsal Cerceve (Evidential Frame Activation)

Kaynak dogrulama modu etkin.

/----------------------------------------------------------------------------/
/* S2 TRIGGER CONDITIONS /
/
----------------------------------------------------------------------------*/

[define|neutral] TRIGGER_POSITIVE := {
keywords: ["meta-tools", "foundry", "workflow"],
context: "user needs meta-tools capability"
} [ground:given] [conf:1.0] [state:confirmed]

/----------------------------------------------------------------------------/
/* S3 CORE CONTENT /
/
----------------------------------------------------------------------------*/

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]"
  • [assert|neutral] quality_threshold: 0.85 [ground:acceptance-criteria] [conf:0.90] [state:provisional]
  • 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]"

Meta-Tools - Tool Creation and Composition Framework

Kanitsal Cerceve (Evidential Frame Activation)

Kaynak dogrulama modu etkin.

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 resou

/*----------------------------------------------------------------------------*/
/* S4 SUCCESS CRITERIA                                                         */
/*----------------------------------------------------------------------------*/

[define|neutral] SUCCESS_CRITERIA := {
  primary: "Skill execution completes successfully",
  quality: "Output meets quality thresholds",
  verification: "Results validated against requirements"
} [ground:given] [conf:1.0] [state:confirmed]

/*----------------------------------------------------------------------------*/
/* S5 MCP INTEGRATION                                                          */
/*----------------------------------------------------------------------------*/

[define|neutral] MCP_INTEGRATION := {
  memory_mcp: "Store execution results and patterns",
  tools: ["mcp__memory-mcp__memory_store", "mcp__memory-mcp__vector_search"]
} [ground:witnessed:mcp-config] [conf:0.95] [state:confirmed]

/*----------------------------------------------------------------------------*/
/* S6 MEMORY NAMESPACE                                                         */
/*----------------------------------------------------------------------------*/

[define|neutral] MEMORY_NAMESPACE := {
  pattern: "skills/foundry/meta-tools/{project}/{timestamp}",
  store: ["executions", "decisions", "patterns"],
  retrieve: ["similar_tasks", "proven_patterns"]
} [ground:system-policy] [conf:1.0] [state:confirmed]

[define|neutral] MEMORY_TAGGING := {
  WHO: "meta-tools-{session_id}",
  WHEN: "ISO8601_timestamp",
  PROJECT: "{project_name}",
  WHY: "skill-execution"
} [ground:system-policy] [conf:1.0] [state:confirmed]

/*----------------------------------------------------------------------------*/
/* S7 SKILL COMPLETION VERIFICATION                                            */
/*----------------------------------------------------------------------------*/

[direct|emphatic] COMPLETION_CHECKLIST := {
  agent_spawning: "Spawn agents via Task()",
  registry_validation: "Use registry agents only",
  todowrite_called: "Track progress with TodoWrite",
  work_delegation: "Delegate to specialized agents"
} [ground:system-policy] [conf:1.0] [state:confirmed]

/*----------------------------------------------------------------------------*/
/* S8 ABSOLUTE RULES                                                           */
/*----------------------------------------------------------------------------*/

[direct|emphatic] RULE_NO_UNICODE := forall(output): NOT(unicode_outside_ascii) [ground:windows-compatibility] [conf:1.0] [state:confirmed]

[direct|emphatic] RULE_EVIDENCE := forall(claim): has(ground) AND has(confidence) [ground:verix-spec] [conf:1.0] [state:confirmed]

[direct|emphatic] RULE_REGISTRY := forall(agent): agent IN AGENT_REGISTRY [ground:system-policy] [conf:1.0] [state:confirmed]

/*----------------------------------------------------------------------------*/
/* PROMISE                                                                     */
/*----------------------------------------------------------------------------*/

[commit|confident] <promise>META_TOOLS_VERILINGUA_VERIX_COMPLIANT</promise> [ground:self-validation] [conf:0.99] [state:confirmed]