skills/workflow-skills/skill-development-workflow/SKILL.md
Automate the initial setup of a new skill. Use when you want to create a new skill from scratch.
npx skillsauth add abcnuts/manus-skills skill-development-workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill automates the initial setup of a new skill, including creating the directory structure and validating it.
To create a new skill called my-new-skill, run:
/home/ubuntu/skills/skill-development-workflow/scripts/run_workflow.sh my-new-skill
This skill performs the following steps in order:
Initialize: Uses the skill-creator skill to create the directory structure for the new skill.
Validate: Uses the skill-creator skill to validate that the new skill's structure is correct.
Discover: The skillz server will automatically discover the new skill, making it available as an MCP tool.
/home/ubuntu/skills/skillz serverAfter running the workflow, you need to:
SKILL.md in your new skill's directory to describe what it does.scripts/ directory.This skill is a "meta-skill" because it's a skill that helps you create other skills. It automates the repetitive parts of skill creation so you can focus on building the unique logic of your new skill.
tools
Generate comprehensive demonstrations showing how to access projects and work across different environments (Manus terminals, personal computers, team collaboration). Use when users ask "how do I access this from another terminal/computer", "how do I share this with my team", "how do I get this on my Mac", or need clarification on Manus persistence vs GitHub usage.
development
Use when you have a spec or requirements for a multi-step task, before touching code
data-ai
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
development
Use when implementing any feature or bugfix, before writing implementation code