home / skills / different-ai / agent-bank / skill-creator

skill-creator skill

safe

This skill helps you create valid OpenCode skills with proper frontmatter and structure, ensuring discoverability and error-free loading.

npx playbooks add skill different-ai/agent-bank --skill skill-creator

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

840 B

---
name: skill-creator
description: Create new OpenCode skills with valid SKILL.md frontmatter.
compatibility: opencode
---

## Purpose

Create well-formed OpenCode skills that load correctly and follow naming rules.

## When to Use

Use this skill when you need to add a new `.opencode/skill/<name>/SKILL.md` file
or fix an existing skill definition.

## Workflow

1. Choose a skill name that matches the directory name and the regex
   `^[a-z0-9]+(-[a-z0-9]+)*$`.
2. Add YAML frontmatter with `name` and `description`.
3. Keep `description` between 1–1024 characters.
4. Add clear sections for purpose, usage, and workflow.
5. Verify the skill is discoverable via the `skill` tool.

## Completion Criteria

- The skill loads without errors.
- Frontmatter fields are valid and minimal.
- Content explains when and how to use the skill.

Overview

This skill creates and validates new OpenCode skill definition files so they load cleanly and follow naming rules. It helps generate minimal, correct frontmatter and clear sections describing purpose, usage, and workflow. Use it to add or fix skill definitions for a CLI-first banking agent environment.

How this skill works

The skill inspects the target skill directory name and enforces a regex-based naming convention. It generates or fixes the YAML frontmatter with required fields, validates description length, and ensures there are explicit sections for purpose, usage, and workflow. Finally, it verifies discoverability with the local skill discovery tool and reports errors to fix.

When to use it

Adding a new skill definition to the codebase
Fixing an existing skill metadata file that fails to load
Ensuring a skill name meets the naming regex and conventions
Preparing skills for discovery by the agent CLI tools
Auditing skill frontmatter for required fields and lengths

Best practices

Choose a directory-aligned name matching ^[a-z0-9]+(-[a-z0-9]+)*$ before creating the file
Keep description between 1 and 1024 characters and be concise about intent
Include explicit Purpose, Usage, and Workflow sections for discoverability
Keep frontmatter minimal—only required fields such as name and description
Run the skill discovery tool after changes to catch loading issues early

Example use cases

Create a new payments skill: validate name, write minimal frontmatter, add usage examples
Repair a malformed skill file that causes the CLI tool to skip the skill
Standardize descriptions across finance-related skills to fit UI constraints
Add workflow steps to a skill so maintainers and agents know how to operate it
Preflight check before merging a skill into the main branch to ensure discoverability

FAQ

What fields are required in the frontmatter?

At minimum include name and description in the YAML frontmatter; keep description concise and within length limits.

How should I choose the skill name?

Use the directory name and follow the regex pattern: lowercase letters and digits, optionally separated by single hyphens.

How do I confirm the skill is discoverable?

Run the local skill discovery CLI tool; the skill should load without errors and appear in the tool's output.