agent-development SKILL.md skillA

agent-development 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/agent-development@git:20261024.772383e

Pins git:20261024.772383e in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

navinspire-ia/navin

Path

navin/skills/agent-development/SKILL.md

Versions recorded

1

Latest version

git:20261024.772383e, committed Oct 24, 2026

Size

12,970 bytes

Repository stars

37

License

AGPL-3.0

Design and write Navin subagents (agents/<name>.md with name, description and examples, tools, model, color, and a system prompt body), and test that Navin delegates to them. Use when the user asks to "create an agent", "add an agent to my plugin", "write a subagent", "agent frontmatter", "when-to-use description", "agent examples", "restrict agent tools", "autonomous agent", or needs agent prompt and triggering best practices.

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

# Agent Development

A subagent is a specialist Navin starts with `spawn(agent="<name>", task="...")`.
It runs in its own context window with its own system prompt, works
autonomously, and returns a report. Use one when a job is self-contained,
benefits from a focused prompt, or would flood the main conversation with
intermediate output.

The `agent-creator` subagent writes an agent from a plain description, using
this skill. `scripts/validate-agent.sh` checks a file.

## File format

```markdown
---
name: test-generator
description: Use this agent when code was written or changed without tests, or when the user asks to "add tests", "cover this module", "write unit tests". Examples:

<example>
Context: The main agent just implemented a parser.
user: "Great, now make sure it is tested."
assistant: "I'll use the test-generator agent to write tests for the parser."
<commentary>New code without tests and an explicit request: delegate.</commentary>
</example>

<example>
user: "Coverage on billing/ is terrible."
assistant: "I'll run the test-generator agent on billing/."
</example>
tools: ["read_file", "grep", "find_files", "write_file", "exec"]
model: inherit
color: green
---
…

Read the whole file at its exact version.

How to install

mdr add navinspire-ia/navin/agent-development@sha256:2739cecf68a48412

[![mdr](https://markdownregistry.com/badge/art_2zpeafm7jrt2uf4y.svg)](https://markdownregistry.com/a/art_2zpeafm7jrt2uf4y)

Versions

The registry has recorded 1 version of this file, committed on Oct 24, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_2zpeafm7jrt2uf4y
GET https://markdownregistry.com/api/v1/resolve?ref=navinspire-ia/navin/agent-development
GET https://markdownregistry.com/api/v1/blob/2739cecf68a484122c7ea9a3150a1c3a23f88c9f2dc2cf772c050e75d14d7e9b

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

Other files named agent-development

Browse by kind, by grade A, or by owner.