sparq-skill-creator

Create and maintain reusable Sparq Skill Units with structured SKILL.md frontmatter.

Updated Feb 24, 2025
One-click install
npx skills add https://github.com/KrisWemet/sparq-connection-lab --skill sparq-skill-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sparq-skill-creator
Source: https://github.com/KrisWemet/sparq-connection-lab/tree/main/.claude/skills/sparq-skill-creator
Command: npx skills add https://github.com/KrisWemet/sparq-connection-lab --skill sparq-skill-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the disciplined creation and evolution of Sparq Skill Units by enforcing a consistent frontmatter+body structure, guiding references, and providing a reusable blueprint for new or updated skills.

Core Features & Use Cases

  • Enforces SKILL.md frontmatter with a name and description, a body under ~500 lines, and optional references/scripts/assets folders.
  • Provides pathways for creating new skills, splitting large skills into focused domains, and auditing the skill library for gaps.
  • Acts as a meta-skill to capture recurring workflows and ensure cohesive skill architecture across the Sparq library.

Quick Start

Provide the desired new or updated Sparq skill and I will generate a complete SKILL.md frontmatter, body, and optional references to formalize it.

Frequently Asked Questions about sparq-skill-creator

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

FAQPage Schema
How do I create a reusable skill with consistent frontmatter and structured content?

Create reusable skill units by generating a SKILL.md file with required frontmatter, a body under 500 lines, and optional references to ensure structured content. This approach enforces consistent architecture across your skill library.

What is the best way to split large skills into focused domains?

Split large skills into focused domains by auditing the existing library for gaps, extracting specific workflows, and generating new SKILL.md files with dedicated routing plans to reference files.

Do I need a routing plan to reference files in a skill library?

Yes, a routing plan is required to reference files. It directs the skill execution logic to optional references, scripts, and assets folders, maintaining cohesive skill architecture across the library.

How does frontmatter structure work when updating an existing skill?

Updating an existing skill requires modifying the SKILL.md frontmatter with a name and description, adjusting the body under 500 lines, and reorganizing optional references to reflect the new workflows.

When should I audit my skill library for gaps?

Audit your skill library for gaps when capturing recurring workflows, planning to split large skills, or ensuring cohesive skill architecture before creating new Sparq Skill Units.