skill-creator

1 stars 2 forks
17
C

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Also in: testing ci cd data analysis

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install mjunaidca/mjs-agent-skills/skill-creator
skilz install mjunaidca/mjs-agent-skills/skill-creator --agent opencode
skilz install mjunaidca/mjs-agent-skills/skill-creator --agent codex
skilz install mjunaidca/mjs-agent-skills/skill-creator --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/mjunaidca/mjs-agent-skills
2. Copy the agent skill directory:
cp -r mjs-agent-skills/docs/taskflow-vault/skills/engineering/skill-creator ~/.claude/skills/

Need detailed installation help? Check our platform-specific guides:

Related Agentic Skills

Agentic Skill Details

Stars
1
Forks
2
Type
Non-Technical
Meta-Domain
development
Primary Domain
github
Market Score
17

Agent Skill Grade

C
Score: 78/100 Click to see breakdown

Score Breakdown

Spec Compliance
12/15
PDA Architecture
22/30
Ease of Use
20/25
Writing Style
9/10
Utility
18/20
Modifiers: -3

Areas to Improve

  • Description needs trigger phrases
  • Missing TOC for 243-line file
  • Lack of concrete input/output examples

Recommendations

  • Add trigger phrases to description for discoverability
  • Add table of contents for files over 100 lines

Graded: 2026-01-24

Developer Feedback

I noticed skill-creator walks developers through building capabilities that extend Claude, but the Progressive Disclosure Architecture could be tightened—there's room to trim token usage without sacrificing clarity.

Links:

The TL;DR

You're at 78/100, solid C-grade territory. This is based on Anthropic's five-pillar rubric for agentic skills. Your strongest area is Writing Style (9/10)—the voice is clear and instructional. Weakest is Progressive Disclosure Architecture (22/30)—the skill needs better token economy and navigation structure for a 243-line file.

What's Working Well

  • Terminology consistency is chef's kiss - You use "bundled resources," "scripts/," and "references/" uniformly throughout. No terminology conflicts.
  • Solid workflow structure - Six clear numbered steps (Understanding → Planning → Initializing → Editing → Packaging → Iterate) give developers a predictable path.
  • Good validation loops - The skill embeds validation throughout: quick_validate.py, package_skill.py, and an explicit iterate step that encourages testing and refinement.
  • Objective, instructional tone - No marketing fluff, purely functional voice. Every sentence earns its place.

The Big One: Missing Table of Contents

At 243 lines, your file exceeds the 100-line threshold where navigation becomes critical. Right now, users have to scroll or search to find sections.

Add a TOC at the top:

## Table of Contents
- [About Skills](#about-skills)
- [Skill Creation Process](#skill-creation-process)
  - [Step 1: Understanding](#step-1-understanding)
  - [Step 2: Planning](#step-2-planning)
  - [Step 3: Initializing](#step-3-initializing)
  - [Step 4: Editing](#step-4-e...

Report Security Issue

Found a security vulnerability in this agent skill?