rune-skill-forge

Creates and validates Rune skills using a test-driven authoring workflow.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-skill-forge-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-skill-forge
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-skill-forge
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-skill-forge-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams building AI agent skills often ship untested SKILL.md files that fail under real-world pressure, duplicate existing skills, or leak workflow details into descriptions so agents skip the full instructions. This Skill enforces a disciplined, test-driven process for authoring and verifying skills before deployment. ## Core Features & Use Cases - TDD Skill Authoring: Write a pressure-test scenario first, observe agent failures without the skill, then write the skill to fix those exact failures and iterate until bulletproof. - Quality Gates and Contracts: Enforces frontmatter rules, description discipline, script output contracts, security models, and behavior evals (evals.md) before any skill ships. - Mesh Integration: Wires new skills into the Rune ecosystem by updating architecture docs, mesh connections, and data-flow mappings. - Use Case: When you need to add a new capability to your Rune agent mesh, invoke this Skill to scan for overlap, baseline-test the problem, author a compliant SKILL.md, and verify it survives adversarial pressure scenarios before committing. ## Quick Start Ask the agent to create a new Rune skill for your desired capability and let it run the full discover-test-write-verify cycle.

Frequently Asked Questions about rune-skill-forge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new Rune skill?

Invoke the skill-forge workflow: scan existing skills for overlap, write a pressure-test scenario, observe agent failures without the skill, then author the SKILL.md targeting those failures. Verify with the same scenario before shipping.

How do I test an AI agent skill before deployment?

Write eval scenarios in evals.md covering happy path, edge cases, and adversarial pressure. Run each with a subagent and confirm no prohibited outputs appear. At least three evals must pass before committing.

What should a SKILL.md description contain?

The description must start with "Use when..." and list only triggering conditions, never the workflow. If an agent could execute the skill from the description alone, it leaks too much and agents will skip the full content.

When should I extend an existing skill instead of creating a new one?

Extend when a skill with more than 70 percent overlap already exists. The discover phase scans the mesh first, and the hard gate blocks creating near-duplicate nodes in favor of deepening existing connections.

What are the limitations of this skill authoring approach?

It requires running baseline and verification subagent tests, costing roughly 3000-8000 tokens per skill across 2-4 iterations. It also only authors and tests skill files, not the underlying tool implementations.