skill-meta

Name: skill-meta
Author: benbrastmckie

Engineering Community

Repo stars 435
Author updated Live
Author repo nvim

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: Engineering
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @benbrastmckie · no license declared
Token usage: Lean
Setup complexity: Guided setup
External API key: Not required
Operating systems: Unspecified (assume cross-platform)
Runtime requirements: No special requirements
Permissions: Read-only
Write / modify
Shell exec
Network behavior: Local-only
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skill-meta.preview

---
name: skill-meta
description: Interactive system builder. Invoke for /meta command to create tasks for .opencode/ system chang…
category: engineering
runtime: no special runtime
---

# skill-meta output preview

## PART A: Task fit
- Use case: Interactive system builder. Invoke for /meta command to create tasks for .opencode/ system changes. Thin wrapper that delegates system building to meta-builder-agent subagent. This skill handles all three modes of /meta: interactive interview, prompt analysis, and system analysis. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Context References / Trigger Conditions / Anti-Bypass Constraint” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Interactive system builder. Invoke for /meta command to create tasks for .opencode/ system changes. Thin wrapper that delegates system building to meta-builder-agent subagent. This skill handles all three modes of /meta: interactive interview, prompt analysis, and system analysis. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Context References / Trigger Conditions / Anti-Bypass Constraint” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: skill-meta
description: Interactive system builder. Invoke for /meta command to create tasks for .opencode/ system chang…
category: engineering
source: benbrastmckie/nvim
---

# skill-meta

## When to use
- Interactive system builder. Invoke for /meta command to create tasks for .opencode/ system changes. Thin wrapper that…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Context References / Trigger Conditions / Anti-Bypass Constraint” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "skill-meta" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Context References / Trigger Conditions / Anti-Bypass Constraint
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Interactive system builder. Invoke for /meta command to create tasks for .opencode/ system changes. Thin wrapper that delegates…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Context References”, “Trigger Conditions”, “Anti-Bypass Constraint”, “Execution”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name skill-meta directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Context References / Trigger Conditions / Anti-Bypass Constraint” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Meta Skill

Thin wrapper that delegates system building to meta-builder-agent subagent. This skill handles all three modes of /meta: interactive interview, prompt analysis, and system analysis.

IMPORTANT: This skill implements the skill-internal postflight pattern. After the subagent returns, this skill handles all postflight operations (git commit if tasks created) before returning. This eliminates the "continue" prompt issue between skill return and orchestrator.

Context References

Reference (do not load eagerly):

Path: .opencode/context/formats/return-metadata-file.md - Metadata file schema
Path: .opencode/context/patterns/postflight-control.md - Marker file protocol
Path: .opencode/context/patterns/file-metadata-exchange.md - File I/O helpers

Note: This skill is a thin wrapper with internal postflight. Context is loaded by the delegated agent.

Trigger Conditions

This skill activates when:

/meta command is invoked (with any arguments)
User requests system building or task creation for .opencode/ changes
System analysis is requested (--analyze flag)

Anti-Bypass Constraint

PROHIBITION: This skill and its delegated agent (meta-builder-agent) MUST NOT write to .opencode/ paths using Write or Edit tools. The /meta workflow creates TASKS only. All .opencode/ file modifications happen through the /implement lifecycle with proper skill delegation.

Detected by: PostToolUse hook validate-meta-write.sh provides corrective context if bypass is attempted.

Legitimate writes: Only specs/ paths (TODO.md, state.json, task directories) are valid write targets for this skill chain.

Execution

1. Input Validation

Validate and classify mode from arguments:

Mode Detection Logic:

# Parse arguments
args="$ARGUMENTS"

# Determine mode
if [ -z "$args" ]; then
  mode="interactive"
elif [ "$args" = "--analyze" ]; then
  mode="analyze"
else
  mode="prompt"
  prompt="$args"
fi

No task_number validation needed - /meta creates new tasks rather than operating on existing ones.

2. Context Preparation

Prepare delegation context:

{
  "session_id": "sess_{timestamp}_{random}",
  "delegation_depth": 1,
  "delegation_path": ["orchestrator", "meta", "skill-meta"],
  "timeout": 7200,
  "mode": "interactive|prompt|analyze",
  "prompt": "{user prompt if mode=prompt, null otherwise}"
}

3. Invoke Subagent

CRITICAL: You MUST use the Task tool to spawn the subagent.

The agent field in this skill's frontmatter specifies the target: meta-builder-agent

Required Tool Invocation:

Tool: Task (NOT Skill)
Parameters:
  - subagent_type: "meta-builder-agent"
  - prompt: [Include mode, prompt if provided, delegation_context]
  - description: "Execute meta building in {mode} mode"

DO NOT use Skill(meta-builder-agent) - this will FAIL. Agents live in .opencode/agents/, not .opencode/skills/. The Skill tool can only invoke skills from .opencode/skills/.

The subagent will:

Load component guides on-demand based on mode
Execute mode-specific workflow:
- Interactive: Run 7-stage interview with AskUserQuestion
- Prompt: Analyze request and propose task breakdown
- Analyze: Inventory existing components and provide recommendations
Create task entries (TODO.md, state.json, task directories) for non-analyze modes
Return standardized JSON result

4. Return Validation

Validate return matches return-metadata-file.md schema:

Status is one of: completed, partial, failed, blocked
Summary is non-empty and <100 tokens
Artifacts array present (task directories for interactive/prompt modes)
Metadata contains session_id, agent_type, delegation info

5. Return Propagation

Return validated result to caller without modification.

Return Format

See .opencode/context/formats/return-metadata-file.md for full specification.

Expected Return: Interactive Mode (tasks created)

{
  "status": "tasks_created",
  "summary": "Created 2 tasks for command creation workflow. Tasks start in NOT STARTED status.",
  "artifacts": [
    {
      "type": "task",
      "path": "specs/430_create_export_command/",
      "summary": "Task directory for new command"
    },
    {
      "type": "task",
      "path": "specs/431_export_command_tests/",
      "summary": "Task directory for tests"
    }
  ],
  "metadata": {
    "session_id": "sess_1736700000_abc123",
    "agent_type": "meta-builder-agent",
    "delegation_depth": 1,
    "delegation_path": ["orchestrator", "meta", "meta-builder-agent"],
    "mode": "interactive",
    "tasks_created": 2,
    "tasks_status": "not_started"
  },
  "next_steps": "Run /research 430 to begin research on first task"
}

Note: Tasks created via /meta start in NOT STARTED status. Run /research N to begin the standard research -> plan -> implement lifecycle.

Expected Return: Analyze Mode (read-only)

{
  "status": "analyzed",
  "summary": "System analysis complete. Found 9 commands, 9 skills, 6 agents, and 15 active tasks.",
  "artifacts": [],
  "metadata": {
    "session_id": "sess_1736700000_xyz789",
    "agent_type": "meta-builder-agent",
    "delegation_depth": 1,
    "delegation_path": ["orchestrator", "meta", "meta-builder-agent"],
    "mode": "analyze",
    "component_counts": {
      "commands": 9,
      "skills": 9,
      "agents": 6,
      "active_tasks": 15
    }
  },
  "next_steps": "Review analysis and run /meta to create tasks if needed"
}

Expected Return: User Cancelled

{
  "status": "cancelled",
  "summary": "User cancelled task creation at confirmation stage. No tasks created.",
  "artifacts": [],
  "metadata": {
    "session_id": "sess_1736700000_def456",
    "agent_type": "meta-builder-agent",
    "delegation_depth": 1,
    "delegation_path": ["orchestrator", "meta", "meta-builder-agent"],
    "mode": "interactive",
    "cancelled": true
  },
  "next_steps": "Run /meta again when ready to create tasks"
}

Error Handling

Input Validation Errors

Return immediately with failed status if arguments are malformed.

Subagent Errors

Pass through the subagent's error return verbatim.

User Cancellation

Return completed status (not failed) when user explicitly cancels at confirmation stage.

Timeout

Return partial status if subagent times out (default 7200s for interactive sessions).

MUST NOT (Postflight Boundary)

After the agent returns, this skill MUST NOT:

Edit .opencode/ files - All system building is done by agent
Create task directories - Task creation is done by agent
Run analysis commands - Analysis is agent work
Write documentation - Artifact creation is agent work
Use AskUserQuestion - User interaction is agent work

The postflight phase is LIMITED TO:

Reading agent return
Git commit (if tasks were created)

Reference: @.opencode/context/standards/postflight-tool-restrictions.md

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add benbrastmckie/nvim/.opencode/extensions/core/skills/skill-meta -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
benbrastmckie/nvim
中文

More by @benbrastmckie

Category & tags

Category Engineering