Skill Creator v2.0

Problem

When maintaining multiple AI agent skills, new skills can overlap with existing ones in function, triggers, and data sources, causing routing conflicts and extra maintenance work. guipi-skill-factory changes skill creation from directly writing a SKILL.md into a workflow that first evaluates the existing skill library before deciding whether to integrate, upgrade, or create a new skill.

Workflow

• Extract the new skill's core function, trigger scenarios, data sources/tools, and target domain, asking follow-up questions when the request is unclear.
• Scan existing skills across functional, trigger, and data-source dimensions, with special attention to high-overlap areas such as content creation, data analysis, and compliance review.
• If overlap is high, suggest integrating the feature into the original skill and incrementing the version. If overlap is partial but adds meaningful scope, suggest an enhanced version. If coverage is low, create a new skill and add a skill-system analysis section.
• Run a security check before creation, flagging hard-coded API Key values, command injection, privacy leakage, over-permissive triggers, and dependency issues. P0 and P1 risks require user confirmation.
• After creation or upgrade, optionally publish to Xiaping, a private GitHub repository, or ClawHub.

Boundaries

It fits personal or team workflows that already maintain a skill library and want consistent naming and versioning. Publishing depends on the corresponding platform skills; without them, creation and upgrade can still proceed. Avoid using new version or enhanced as the skill name; version changes should appear in the version number or changelog.