skill-creator

Create or update modular AgentSkills with SKILL.md frontmatter and progressive disclosure.

335|2|Updated May 6, 2026
One-click install
npx skills add https://github.com/THU-SAGE/syll --skill skill-creator-thu-sage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/THU-SAGE/syll/tree/main/syll/skills/skill-creator
Command: npx skills add https://github.com/THU-SAGE/syll --skill skill-creator-thu-sage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you design high-quality Syll skills by turning domain needs into clear, efficient, modular skill packages that an agent can reliably use.

Core Features & Use Cases

  • Skill anatomy and requirements: Explains how to structure SKILL.md with the mandatory name/description frontmatter and keep the body operational and trigger-relevant.
  • Progressive disclosure guidance: Recommends keeping metadata lightweight, loading the body only when triggered, and pulling larger material from references/resources only when needed.
  • Packaging and iteration workflow: Provides a step-by-step process for initializing, implementing, packaging, and iterating skills to improve real usage.

Quick Start

Create a new skill directory named skill-creator with a valid SKILL.md frontmatter and then refine the workflow instructions to match the exact scenarios you want the agent to handle.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I structure a SKILL.md file for agent onboarding?

To structure a SKILL.md file for agent onboarding, include mandatory name and description YAML frontmatter, then keep the body operational and trigger-relevant. This ensures the agent reliably discovers and uses the modular workflow instructions.

What is progressive disclosure in skill design?

Progressive disclosure in skill design is an approach that keeps metadata lightweight, loads the SKILL.md body only when triggered, and pulls larger material from bundled references or resources only when needed to control context size.

How to package modular workflows with bundled assets?

Package modular workflows by initializing a skill directory, implementing the operational instructions, bundling necessary scripts or assets, and then iterating the workflow to match exact scenarios. This workflow ensures skills remain usable and discoverable.

What is the best way to design agent skills that need external scripts?

The best way to design agent skills that need external scripts is to apply modular packaging principles, keeping the SKILL.md frontmatter lightweight and pulling larger scripts from bundled resources only when needed during execution.

Does packaging a skill require specific dependencies?

Packaging a skill does not require external dependencies. It relies on adhering to the SKILL.md schema, structuring YAML frontmatter correctly, and following a step-by-step initialization and iteration workflow to ensure discoverability.

When should I not use progressive disclosure for skill design?

You should not use progressive disclosure for skill design when your operational instructions are extremely minimal and lack large bundled resources, as the overhead of modular loading provides no context size benefit for simple skills.