Skill Factory Pro

Problem

Agent skills often drift across D:/Skills, .qclaw/skills, and workspace-main/skills, while whitelist references break after deletions or renames. New skills can duplicate existing ones, inaccurate description fields hurt routing, and long main files waste tokens. This skill turns skill creation into an auditable workflow.

How It Works

It proceeds by phases: three-question scoping defines trigger context, value, and monetization; existing-skill scanning decides whether to merge or create a new skill. The generation stage uses domain agents to fill knowledge gaps and outputs SKILL.md, references/, and packaging notes. Before delivery, it checks whether the description covers feature keywords and triggers, whether the main file stays compact, and whether a quality score meets the publish threshold.

Boundaries

It treats D:/Skills as the manual source, then reverse-syncs the other two directories and cleans whitelist entries. The governance module is read-only by default and requires confirmation before changes. If existing skills differ substantially, creating a new skill may be cleaner; for one-off use without publishing or shared maintenance, some monetization and sync steps may be heavier than needed.