Skip to content

himself65/finance-skills / plugins/skill-creator/skills/skill-creator

skill-creator

Verified

Create, improve, and evaluate agent skills (SKILL.md plus reference files). Use this skill whenever the user wants to build, scaffold, or design a new skill, improve or fix an existing skill that isn't working well, score or benchmark a skill's quality or run evals on it, or turn a repeated manual workflow into a skill ("I keep doing X manually", "can you remember how to do X", "turn this into a skill").

references/frontmatter-guide.md

View on GitHub
# SKILL.md Frontmatter Reference

Complete field reference for the YAML frontmatter block that starts every SKILL.md file.

## Required Fields

### `name`
- **Type:** string
- **Max length:** 64 characters
- **Pattern:** `^[a-z0-9][a-z0-9._-]*$` (lowercase alphanumeric, hyphens, dots, underscores)
- **Purpose:** Unique identifier used in slash commands, file paths, and skill references

```yaml
name: my-skill-name
```

### `description`
- **Type:** string (multi-line with `>` recommended)
- **Max length:** 1024 characters
- **Purpose:** Controls when the skill activates. This is the most important field for skill quality.

```yaml
description: >
  [What it does] Analyze stocks using the SEPA methodology.
  [Intent categories + vocabulary] SEPA, Minervini, VCP, trend template, Stage 2, pivot point.
  [Scoped sideways entries] "should I buy this stock" about a growth or momentum name.
  [Context triggers] When user shares a chart, mentions swing trading criteria.
  [Boundaries] For X, use sibling-skill instead.
```

**Writing a high-quality description:**

1. Start with a concrete action verb: "Analyze", "Generate", "Fetch", "Evaluate" (not "Use" or "Handle")
2. Name specific tools/APIs: "via yfinance", "using the Fintel API"
3. Name every category of request the skill serves, with the distinctive terms users will use — both expert vocabulary and plain-language requests
4. Scope sideways entry points to their context ("should I buy this stock" about a growth name), so they don't fire everywhere
5. Point to sibling skills for neighboring requests, and state read-only limits where relevant

The description rides along in every request, so it is the one place where calibrated urgency ("use this skill whenever...") belongs. Keep behavioral instructions — how to do the work — in the body.

**Common mistakes:**
- Too short: "Analyze stocks" — won't trigger on specific requests
- Too generic: "Financial analysis tool" — triggers on everything, useful for nothing
- Missing beginner terms: Only expert jargon excludes most users
- Synonym lists: ten quoted phrasings of the same request cost tokens in every session and generalize worse than naming the category once
- Behavior in the description: "default to running all three methods" belongs in the body

## Optional Fields

### `version`
Semantic version for the skill. Useful for tracking changes.
```yaml
version: 1.0.0
```

### `author`
Creator name or handle.
```yaml
author: himself65
```

### `license`
License identifier.
```yaml
license: MIT
```

### `platforms`
Restrict to specific operating systems. Omit to load on all platforms (default).
```yaml
platforms: [macos, linux]   # Valid values: macos, linux, windows
```

### `required_environment_variables`
Declare API keys or tokens the skill needs. These are secrets stored in `~/.hermes/.env`.

```yaml
required_environment_variables:
  - name: FINTEL_API_KEY
    prompt: "Fintel API key"
    help: "Get one at https://fintel.io/api"
    required_for: "API access"
```

Fields per entry:
- `name` (required) — environment variable name
- `prompt` (optional) — text shown when asking the user
- `help` (optional) — URL or help text for obtaining the value
- `required_for` (optional) — which feature needs this variable

### `required_credential_files`
Declare file-based credentials (OAuth tokens, certificates).

```yaml
required_credential_files:
  - path: google_token.json
    description: Google OAuth2 token (created by setup script)
```

### `metadata.hermes`
Hermes-specific metadata for discovery, activation, and configuration.

```yaml
metadata:
  hermes:
    tags: [Finance, Market Analysis, Options]
    related_skills: [yfinance-data, earnings-preview]
    category: market-analysis
```

### Conditional Activation

Control when the skill appears in the system prompt:

```yaml
metadata:
  hermes:
    requires_toolsets: [web]              # Hide if web toolset NOT active
    requires_tools: [web_search]          # Hide if web_search NOT available
    fallback_for_toolsets: [browser]      # Hide if browser IS active
    fallback_for_tools: [browser_navigate] # Hide if browser_navigate IS available
```

| Field | Logic |
|---|---|
| `requires_toolsets` | Hidden when ANY listed toolset is unavailable |
| `requires_tools` | Hidden when ANY listed tool is unavailable |
| `fallback_for_toolsets` | Hidden when ANY listed toolset IS available |
| `fallback_for_tools` | Hidden when ANY listed tool IS available |

### Config Settings

Non-secret settings stored in `config.yaml`:

```yaml
metadata:
  hermes:
    config:
      - key: wiki.path
        description: Path to knowledge base directory
        default: "~/wiki"
        prompt: "Wiki directory path"
```

## Complete Frontmatter Example

```yaml
---
name: sepa-strategy
description: >
  Analyze stocks using Mark Minervini's SEPA methodology.
  Triggers: SEPA, Minervini, VCP, trend template, Stage 2, pivot point,
  superperformance, bullish stacking, breakout volume, cup-with-handle,
  "should I buy this stock", "is this a good setup", growth stock screening.
version: 1.0.0
author: himself65
license: MIT
metadata:
  hermes:
    tags: [Finance, Trading, Technical Analysis]
    related_skills: [yfinance-data, stock-correlation]
---
```

## Size Constraints Summary

| Field | Limit |
|---|---|
| `name` | 64 characters |
| `description` | 1024 characters |
| SKILL.md total content | 100,000 characters |
| Supporting files | 1 MiB each |
| Category name | 64 characters, single directory level |
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall