build-skill

Creates and audits EVA runtime skills with safe SKILL.md metadata and scoped guidance.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/raulisai/eva02 --skill build-skill-raulisai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: build-skill
Source: https://github.com/raulisai/eva02/tree/main/apps/eva-core/src/skills/build-skill
Command: npx skills add https://github.com/raulisai/eva02 --skill build-skill-raulisai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams extending the EVA agentic platform need a consistent, safe way to create, rename, refactor, or retire runtime skills without duplicating existing capabilities or bypassing tenant isolation and approval gates. ## Core Features & Use Cases - Standardized Skill Authoring: Enforces a canonical directory shape with SKILL.md frontmatter, optional scripts, references, and templates. - Safety-First Guardrails: Embeds the EVA Runtime Skill Policy, requiring org_id tenant boundaries, secret protection, and explicit approval for external writes or destructive actions. - Audit and Removal Criteria: Defines when to update, merge, or delete skills that duplicate others, leak credentials, or skip approval gates. - Use Case: When a recurring workflow emerges in EVA, use this Skill to scaffold a new runtime skill with narrow trigger wording, then verify it with the skills-runtime test suite. ## Quick Start Ask EVA to create a new runtime skill for your repeatable workflow and have it validated against the runtime skill policy.

Frequently Asked Questions about build-skill

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

FAQPage Schema
How do I create a new EVA runtime skill?

Create a focused directory containing a SKILL.md file with YAML frontmatter defining a name and description, then add optional scripts, references, or templates. Follow the workflow of checking for duplicates, writing narrow trigger wording, and verifying with the skills-runtime test suite.

What frontmatter does a SKILL.md file require?

SKILL.md requires YAML frontmatter with a name and description field. The name uses lowercase letters, digits, and hyphens, and the description should state what EVA uses the skill for, including trigger wording.

When should an EVA skill be deleted instead of kept?

Delete a skill when it sends messages or money actions without an approval gate, requires plaintext credentials, duplicates another skill, depends on private framework paths, or encourages unapproved production deploys and destructive commands.

How do I verify changes to an EVA runtime skill?

Run the skills-runtime test suite from the apps/eva-core directory using npm test with the skills-runtime.spec.ts file. Also verify frontmatter validity, relative references, and risk language before shipping.

What safety constraints apply to EVA runtime skills?

Skills must preserve org_id tenant boundaries, never expose secrets, and require explicit approval before external writes, destructive actions, production changes, money actions, messaging, installs, or credential changes, per the Runtime Skill Policy.