x-skill-bundles

Structure Level85 skill bundles with YAML frontmatter and auditable scripts.

2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/pure-golang/level85 --skill x-skill-bundles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-skill-bundles
Source: https://github.com/pure-golang/level85/tree/main/.agents/skills/x-skill-bundles
Command: npx skills add https://github.com/pure-golang/level85 --skill x-skill-bundles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents skill bundles from drifting into vague, hard-to-audit, or incorrectly organized guidance by enforcing Level85-specific conventions for what must stay in SKILL.md and what may go into scripts or assets.

Core Features & Use Cases

  • Clarifies SKILL.md vs bundled resources: keeps conditions, workflow, boundaries, and examples in SKILL.md while allowing assets/scripts only when they remain transparent and optionally auditable.
  • Improves auditability and reliability: limits scripts to small, deterministic, and easy-to-check operations, and discourages “generator magic” that hides project logic.
  • Reduces dependency on external truth: blocks referencing benchmark/“reference” repositories as the source of truth and restricts allowed adapter/platform dependencies to real local contracts.
  • Use case: when creating or revising a local skill in .agents/skills, you use this bundle rule-set with skill-creator to ensure the resulting skill is self-contained, consistent, and unlikely to cause incorrect code generation.

Quick Start

Use x-skill-bundles together with skill-creator to author or refactor a local skill’s SKILL.md in .agents/skills so it stays self-contained and follows Level85 constraints.

Frequently Asked Questions about x-skill-bundles

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

FAQPage Schema
What should go in SKILL.md versus scripts or assets when structuring a skill bundle?

SKILL.md should contain conditions, workflow, boundaries, and examples, while scripts and assets are reserved for small, deterministic, transparent helper operations that remain easy to audit.

How do I keep skill authoring auditable and prevent hidden logic in project conventions?

To keep skill authoring auditable, restrict scripts to small deterministic operations and avoid generator magic that hides project logic, ensuring all operational instructions remain transparent in SKILL.md.

Can I reference external benchmark repositories as the source of truth for local skills?

No, you cannot reference external benchmark or reference repositories as the source of truth. Skill bundles must be self-contained and restrict dependencies to real local contracts only.

How do I write YAML frontmatter for a skill in .agents/skills?

YAML frontmatter for a skill in .agents/skills requires name and description fields to define the skill's identity and purpose before detailing operational instructions in SKILL.md.

What is the best way to ensure a local skill is self-contained and follows project conventions?

The best way to ensure a local skill is self-contained is to apply project-specific bundle rules during authoring, keeping all required rules in SKILL.md and validating against Level85 constraints.

Are there limitations on using scripts within skill bundles for code generation?

Yes, scripts within skill bundles are limited to small, deterministic, and easy-to-check operations to prevent hidden logic and ensure the generated code remains reliable and auditable.