fullstack-dev SKILL.md skillF
fullstack-dev from navinspire-ia/navin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add navinspire-ia/navin/fullstack-dev@git:20261024.772383ePins git:20261024.772383e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- F, 15 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- navinspire-ia/navin
- Path
navin/skills/fullstack-dev/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261024.772383e, committed Oct 24, 2026
- First version recorded
- Jul 23, 2026
- Size
- 23,253 bytes
- Repository stars
- 37
- License
- AGPL-3.0
Build, run, and debug frontend, backend, and database projects end to end in the workspace (plan, investigate, code, execute, verify). Use for Dev mode sessions, scaffolding apps, fixing bugs, and running dev servers.
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
# Full-Stack Developer Work like a senior engineer inside the workspace: plan before coding, investigate before changing, verify after every step. This is the core skill behind Dev mode sessions. ## When to use - The user opens a Dev session or asks to build/modify an application (frontend, backend, API, database). - The user reports a bug, a failing build, or unexpected behavior in a project. - The user asks to scaffold a new project (Vite/React, Node/Express, Python/FastAPI, etc.). ## Operating loop 1. **Plan** - Restate the goal. For non-trivial tasks, write a short numbered plan (steps, files touched, risks) before editing anything. Keep the plan visible and update it as you go. System architecture in that plan uses `archify`. 2. **Investigate** - Read the relevant files with `read_file` / `list_dir` before changing them. Use `exec` with `rg` for code search. Never guess an API that exists in the repo - check it. 3. **Code** - Make focused edits with `edit_file` / `write_file`. Follow the project's existing conventions (imports, formatting, naming). Small commits of change, one concern at a time. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ezdavxsczlmfzt6r/6be7644113171663eecb224c6d9423c99e03dd02e9c246effde8a1240f4d67a6.json
Then /plugin install fullstack-dev@markdownregistry-ezdavxsczlmfzt6r in Claude Code. It installs git:20261024.772383e, the one graded F here, pinned to the commit it was graded at, and leaves it there.
mdr add navinspire-ia/navin/fullstack-dev@sha256:6be7644113171663The line at the top of this page pins the label git:20261024.772383e, 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_ezdavxsczlmfzt6r)
1 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 navinspire-ia/navin/fullstack-dev 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 fullstack-dev from somewhere else? Ask it: where did my fullstack-dev 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 3 versions of this file, between Jul 23, 2026 and Oct 24, 2026, about one every 47 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.772383e latest | 2026-10-24 | 772383e | 23,253 B | F | view · diff |
| git:20260906.85504a9 | 2026-09-06 | 85504a9 | 9,739 B | F | view · diff |
| git:20260723.de898c0 | 2026-07-23 | de898c0 | 3,668 B | F | view |
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/fullstack-dev/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
- FAIL, critical: No zero-width or bidi control characters (matched: )
- fail: No instruction to read or print local credentials (matched: read from `.env`, documented in `.env)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (23253 bytes)
- 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 base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
navinspire-ia/navin · 37 stars · license AGPL-3.0 · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ezdavxsczlmfzt6r GET https://markdownregistry.com/api/v1/resolve?ref=navinspire-ia/navin/fullstack-dev GET https://markdownregistry.com/api/v1/blob/6be7644113171663eecb224c6d9423c99e03dd02e9c246effde8a1240f4d67a6
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 navinspire-ia/navin
Every file in navinspire-ia/navin