deepen-plan SKILL.md skillA
deepen-plan from shyamsridhar123/kevin-copilot is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add shyamsridhar123/kevin-copilot/deepen-plan@git:20260422.d562cf9Pins git:20260422.d562cf9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- shyamsridhar123/kevin-copilot
- Path
.github/skills/deepen-plan/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260422.d562cf9, committed Apr 22, 2026
- Size
- 18,021 bytes
- Repository stars
- 8
- License
- MIT
Enhance a plan with parallel research agents for each section to add depth, best practices, and implementation details.
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
## Arguments [path to plan file] # Deepen Plan - Power Enhancement Mode ## Introduction **Note: The current year is 2026.** Use this when searching for recent documentation and best practices. This command takes an existing plan (from `/ce-plan`) and enhances each section with parallel research agents. Each major element gets its own dedicated research sub-agent to find: - Best practices and industry patterns - Performance optimizations - UI/UX improvements (if applicable) - Quality enhancements and edge cases - Real-world implementation examples The result is a deeply grounded, production-ready plan with concrete implementation details. ## Plan File <plan_path> #$ARGUMENTS </plan_path> **If the plan path above is empty:** 1. Check for recent plans: `ls -la docs/plans/` 2. Ask the user: "Which plan would you like to deepen? Please provide the path (e.g., `docs/plans/2026-01-15-feat-my-feature-plan.md`)." Do not proceed until you have a valid plan file path. ## Main Tasks ### 1. Parse and Analyze Plan Structure <thinking> First, read and parse the plan to identify each major section that can be enhanced with research. </thinking> **Read the plan file and extract:** …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_kbouuzoxhlu2mmcp/fd6803b60860815321c999b69b151a6ed9ddbb86e264fa524a6385a89fcc28df.json
Then /plugin install deepen-plan@markdownregistry-kbouuzoxhlu2mmcp in Claude Code. It installs git:20260422.d562cf9, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add shyamsridhar123/kevin-copilot/deepen-plan@sha256:fd6803b608608153The line at the top of this page pins the label git:20260422.d562cf9, 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_kbouuzoxhlu2mmcp)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in shyamsridhar123/kevin-copilot/deepen-plan since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of deepen-plan from somewhere else? Ask it: where did my deepen-plan come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Apr 22, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/deepen-plan/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (18021 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
shyamsridhar123/kevin-copilot · 8 stars · license MIT · pushed 2026-08-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kbouuzoxhlu2mmcp GET https://markdownregistry.com/api/v1/resolve?ref=shyamsridhar123/kevin-copilot/deepen-plan GET https://markdownregistry.com/api/v1/blob/fd6803b60860815321c999b69b151a6ed9ddbb86e264fa524a6385a89fcc28df
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.
More from shyamsridhar123/kevin-copilot
Every file in shyamsridhar123/kevin-copilot
Other files named deepen-plan
Browse by kind, by grade A, or by owner.
Kept in .github/skills, the folder GitHub Copilot reads. More agent skills for GitHub Copilot.