sc

Create and maintain structured skills with valid SKILL.md frontmatter.

21|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/kevinslin/skills --skill sc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc
Source: https://github.com/kevinslin/skills/tree/main/active/sc
Command: npx skills add https://github.com/kevinslin/skills --skill sc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides guidance for creating effective skills and SKILL.md content, including edits to existing skills, adding workflows/tools, or changing triggers. It helps ensure skills are consistently structured and easy to activate.

Core Features & Use Cases

  • Structured guidance for designing skills with clear frontmatter conventions and body content.
  • Examples and templates to standardize naming, dependencies, and resource organization.
  • Reference patterns for workflows, scripts, and references to maintainability and scalability.

Quick Start

Follow the structure described in this skill's SKILL.md to begin creating or updating a skill, starting with defining frontmatter and a clear body outline.

Frequently Asked Questions about sc

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

FAQPage Schema
How do I create a well-structured skill and define its frontmatter?

To create a skill, define its SKILL.md frontmatter by specifying the required name, description, and dependencies fields, then outline the body content to ensure the skill is consistently structured and easy to activate.

What frontmatter fields are required for valid skill documentation?

Valid skill documentation requires frontmatter fields for name, description, and dependencies to enforce structural validity and coordinate optional resources like scripts, references, and assets across all allowed skill roots.

What is the best way to update existing skills and add new workflows?

The best way to update existing skills is to follow standardized templates for naming and resource organization, editing the SKILL.md body content to add workflows, tools, or change triggers while maintaining frontmatter validity.

How do I manage skill dependencies and package optional resources?

Manage skill dependencies and package optional resources by using the provided tooling for dependency syncing, ensuring that scripts, references, and assets are properly coordinated alongside the required frontmatter fields.

Can I use standard templates to organize skill scripts and references?

Yes, you can use reference patterns and templates to standardize naming, organize scripts and references, and maintain scalability and maintainability across all allowed skill roots in your documentation conventions.