dev-new-tool SKILL.md skillA
dev-new-tool from jackchuka/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jackchuka/skills/dev-new-tool@git:20260604.0da3398Pins git:20260604.0da3398 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jackchuka/skills
- Path
dev-new-tool/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260604.0da3398, committed Jun 4, 2026
- First version recorded
- Mar 11, 2026
- Size
- 6,569 bytes
- Repository stars
- 15
- License
- MIT
End-to-end workflow for taking a new tool idea from research to working MVP. Use when the user has an idea for a CLI tool, library, or small project and wants to go from concept to initial implementation. Triggers on "I have an idea for a tool", "build a new CLI", "create a new project", "kickoff new tool", "I want to build", "let's build a new", "新しいツールを作りたい", "CLIを作る".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# New Tool Kickoff A structured workflow for turning a tool idea into a working MVP. Covers the full cycle: research existing solutions, brainstorm approach, write a plan, scaffold the project, build core features, and write documentation. ## When to Use - User says "I have an idea for a tool/CLI/library" - User wants to start a new project from scratch - User wants to research feasibility before building - Greenfield development of a focused tool or CLI ## Workflow ### Phase 1: Research (Stop point: get user approval before Phase 2) **Goal:** Understand the landscape before building. 1. **Clarify the idea**: Ask what problem the tool solves, who uses it, and what the core workflow looks like 2. **Search for existing tools**: Web search for similar tools, libraries, or CLIs 3. **Evaluate alternatives**: For each existing tool found: - What does it do well? - What gaps or limitations does it have? - Is it actively maintained? 4. **API/Integration research**: If the tool integrates with external services, research their APIs: - Authentication methods - Rate limits and pagination - Data models and available endpoints …
Read the whole file at its exact version.
How to install
mdr add jackchuka/skills/dev-new-tool@sha256:f089554882740d53The line at the top of this page pins the label git:20260604.0da3398, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_mb3n3fsn7c2hm775)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Mar 11, 2026 and Jun 4, 2026, about one every 28 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260604.0da3398 latest | 2026-06-04 | 0da3398 | 6,569 B | A | view · diff |
| git:20260421.19f33a5 | 2026-04-21 | 19f33a5 | 6,551 B | A | view · diff |
| git:20260321.fb3b945 | 2026-03-21 | fb3b945 | 6,538 B | A | view · diff |
| git:20260311.2835406 | 2026-03-11 | 2835406 | 6,494 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6569 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jackchuka/skills · 15 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mb3n3fsn7c2hm775 GET https://markdownregistry.com/api/v1/resolve?ref=jackchuka/skills/dev-new-tool GET https://markdownregistry.com/api/v1/blob/f089554882740d531c7e06cc34b2c37c7f543d985e13284111ed70ff87d1bf99
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.