skills.rest
galligan
galliganCOMMUNITY
Explore all skills by this author ā†’
Websiteš•@mgGitHub

skillstash-management

Validate and manage Skillstash skills with frontmatter and structure checks.

1|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/galligan/skillstash --skill skillstash-management
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: skillstash-management
Source: https://github.com/galligan/skillstash/tree/main/.agents/skills/skillstash-management
Command: npx skills add https://github.com/galligan/skillstash --skill skillstash-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill tells users how to create, validate, and manage skills in this Skillstash instance.

Repository Structure

skillstash/
ā”œā”€ā”€ skills/                    # All skills live here
ā”‚   ā””ā”€ā”€ my-skill/
ā”‚       ā”œā”€ā”€ SKILL.md           # Required - skill definition
ā”‚       ā”œā”€ā”€ references/        # Optional - docs, specs
ā”‚       ā”œā”€ā”€ scripts/           # Optional - executable helpers
ā”‚       ā””ā”€ā”€ assets/            # Optional - templates, configs
ā”œā”€ā”€ .skillstash/
ā”‚   ā””ā”€ā”€ config.yml             # Skillstash configuration
ā”œā”€ā”€ docs/                      # Skillstash documentation
ā”œā”€ā”€ scripts/                   # Skillstash automation
ā””ā”€ā”€ .agents/                   # Agent instructions

Creating a Skill

1. Create the Directory

mkdir -p skills/my-skill-name

Use kebab-case for directory names.

2. Create SKILL.md

Every skill requires a SKILL.md with YAML frontmatter:

---
name: my-skill-name
description: Brief one-line description of what this skill does
---

# My Skill Name

## When to Use This Skill

Describe trigger conditions.

## What This Skill Does

Step-by-step instructions.

## Examples

Concrete usage examples.

3. Required Frontmatter

| Field | Description | |-------|-------------| | name | Must match directory name exactly (kebab-case) | | description | One-line summary for discovery |

4. Optional Frontmatter

| Field | Description | |-------|-------------| | version | Semver (e.g., 1.0.0) | | author | GitHub username | | tags | Array for categorization | | status | experimental, stable, deprecated | ā€¦

Frequently Asked Questions about skillstash-management

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

FAQPage Schema
How do I create a new skill in Skillstash?ā–¼

Create a new skill by making a kebab-case directory under `skills/`, then add a `SKILL.md` file with YAML frontmatter containing `name` and `description` fields. The directory name must match the frontmatter `name` exactly to ensure proper validation and discoverability.

What frontmatter fields are required in SKILL.md?ā–¼

Every SKILL.md requires two frontmatter fields: `name` (must match the directory name in kebab-case) and `description` (a one-line summary). Optional fields include `version`, `author`, `tags`, and `status` to support categorization and workflow tracking.

How do I validate that my skill meets repository standards?ā–¼

Validation checks that your skill's directory name matches its frontmatter `name`, enforces kebab-case naming, confirms SKILL.md exists with correct frontmatter, and verifies line limits are respected. Running validation before pushing ensures your skill is standards-compliant and merge-ready.

Can I use spaces or uppercase letters in my skill directory name?ā–¼

No. Skill directory names must use kebab-case (lowercase with hyphens only), and the name must match exactly what you put in the `name` frontmatter field. This naming convention ensures consistent skill discovery and repository structure across all workflows.

What should I include in the optional skills directory structure?ā–¼

Beyond the required `SKILL.md`, you can add optional subdirectories: `references/` for documentation and specs, `scripts/` for executable helpers, and `assets/` for templates and configs. These support richer skill implementations while keeping the core structure clean and predictable.

How do I prepare my skill for merging into the repository?ā–¼

Before merging, run validation to confirm frontmatter correctness, kebab-case naming, and line limits. Check that your branch follows naming conventions and that all required fields are present. This workflow check ensures your skill integrates cleanly and maintains repository standards.

Related Skills

tneztnez

bootstrap

Initialize the .docent directory structure and configuration for new projects.

Community
Basic
dnvitidnviti
11

git-publish

Merge develop into main and push both branches to origin.

Community
Intermediate
aimskraimskr

github-operator

Automate Git operations with branch naming and conventional commits.

Official
Advanced
XiongJingzhiXiongJingzhi

different-name

Flag skills whose SKILL.md name field mismatches the directory name.

Community
Basic