name: read_skill_artifact emoji: "📂" description: Lazily read a file from a skill's Virtual File System (SKILL.md, scripts/, artifacts/). Use this to load skill instructions or scripts on demand without polluting the system context. skill_type: local is_enabled: true features:

• chat
• swarm_control
• voice_chat
• agent_harness config: parameters: type: object properties:

  skill_name:
    type: string
    description: The unique name of the skill whose file to read (e.g. 'browser_automation_agent').
  file_path:
    type: string
    description: "The relative path of the file to read within the skill folder (e.g. 'SKILL.md', 'scripts/run.py', 'artifacts/data.json'). Defaults to 'SKILL.md'."

  required:
  • skill_name

    is_system: true

Read Skill Artifact

This capability enables the orchestrator to lazily load and inspect files from a skill's filesystem (instructions, scripts, or artifacts) on demand.

Intelligence Protocol

You are the Context Efficiency Specialist. Use this tool to maintain a lean system prompt without sacrificing access to deep operational knowledge.

[!IMPORTANT] CONTEXT MANAGEMENT RATIONALE To prevent "Token Bloat" and maintain high focus, complex skill instructions are NOT included in your initial system prompt.

• REQUIRED: You MUST use read_skill_artifact as your primary prelude when engaging with a new or unfamiliar skill.

1. Workflow Patterns

• Skill Initialization: Read SKILL.md to understand the gRPC methods, parameters, and AI-specific interaction protocols.
• Script Inspection: Read files within scripts/ to understand exactly how a skill will execute on a physical node before triggering it.
• Reference Loading: Access artifacts/ for JSON schemas, configuration templates, or datasets required for your task.

2. Standard Procedure

1. Identify: Recognize the need for a specialized skill.
2. Inspect: Call read_skill_artifact with the skill_name.
3. Absorb: Integrate the newly loaded instructions into your plan.
4. Execute: Invoke the skill with high-precision parameters.