skill-name

Create reusable skill metadata with SKILL.md frontmatter and operational instructions.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/robwestz/ob1_workspace --skill skill-name-robwestz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-name
Source: https://github.com/robwestz/ob1_workspace/tree/main/skills/_template
Command: npx skills add https://github.com/robwestz/ob1_workspace --skill skill-name-robwestz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps authors turn recurring workflows into a reusable skill package with clear triggers, instructions, and metadata for discovery.

Core Features & Use Cases

  • Skill Scaffolding: Provides a standard structure for defining a skill entry point, operational guidance, and supporting metadata.
  • Authoring Guidance: Clarifies what to include in frontmatter, the main process steps, and expected output so the skill is easy to maintain.
  • Use Case: Use it when you want to create a new reusable assistant workflow for a specific task, client, or team process.

Quick Start

Ask the assistant to draft a new skill by filling in the SKILL.md frontmatter and writing concise operating instructions for your workflow.

Frequently Asked Questions about skill-name

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

FAQPage Schema
How do I create a reusable skill template from a recurring workflow?

To create a reusable skill template, draft a SKILL.md file containing frontmatter with a valid name and description, then define triggers and operational instructions for the workflow. This scaffolding packages the process for discovery.

What metadata is required in frontmatter for skill authoring?

Skill authoring requires frontmatter containing valid name and description fields. Optional metadata fields for components, dependencies, and safety review can also be included to provide operational guidance and support client adaptation.

When do I need to scaffold a skill package?

You need to scaffold a skill package when you want to turn a specific task, client process, or team workflow into a reusable assistant skill with clear triggers and maintenance instructions.

What is the best way to structure operational instructions for a new skill?

The best way to structure operational instructions is to write concise process steps and expected outputs directly within the SKILL.md file, ensuring the workflow is easy to maintain and discoverable.

Can I include optional dependencies when defining skill metadata?

Yes, you can include optional dependencies when defining skill metadata. The frontmatter supports optional fields for components, dependencies, and safety review alongside the required name and description.