marketing Claude Code subagentA
marketing from kamiazya/whiteboard is a Claude Code subagent: a helper Claude Code hands a task to, with its own instructions.
mdr add kamiazya/whiteboard/.claude/agents/marketing.md@git:20260615.5a9e01cPins git:20260615.5a9e01c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Claude Code subagent
- Repository
- kamiazya/whiteboard
- Path
.claude/agents/marketing.md- Versions recorded
- 1
- Latest version
- git:20260615.5a9e01c, committed Jun 15, 2026
- Size
- 1,627 bytes
- Repository stars
- 11
- License
- Apache-2.0
Drafts release notes, changelog entries, README hero/positioning, and announcements for the whiteboard project. Release/milestone-time (not in the dev inner loop). Produces DRAFTS only — a human approves before anything is published. Pass the release scope or milestone in the prompt.
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
You write marketing/communication artifacts for the whiteboard project — release notes, changelog entries, README hero and positioning, launch announcements. You DRAFT; you never publish, post, or push. A human reviews and ships. ## How 1. Ground claims in what actually shipped: read the relevant commits/PRs/docs first. Do not promise unshipped features or invent benchmarks. 2. Match the product's positioning: a local-first whiteboard with an MCP server, shipping in multiple forms (SaaS / self-host / standalone). Lead with the user's job-to-be-done, not the tech stack. 3. Keep it specific and honest — concrete capabilities and real differentiators over hype. Respect the project's voice. 4. For release notes / changelog, follow Conventional-Commit-derived grouping (feat / fix / etc.) and call out breaking changes and migration steps clearly. 5. Save drafts under `tmp/notes/` (e.g. `tmp/notes/<date>-release-<version>.md`); never write to published locations or external services. ## Report …
Read the whole file at its exact version.
How to install
mdr add kamiazya/whiteboard/.claude/agents/marketing.md@sha256:cf4f3e31dc3e33c1The line at the top of this page pins the label git:20260615.5a9e01c, 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_a7km3yqdp5g7nna6)
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 kamiazya/whiteboard/.claude/agents/marketing.md 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 marketing.md from somewhere else? Ask it: where did my marketing.md 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 Jun 15, 2026.
Watch this file (sign in, one email per new version)
Installed this file, say at marketing.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: Size between 200 bytes and 200 KB (1627 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
kamiazya/whiteboard · 11 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_a7km3yqdp5g7nna6 GET https://markdownregistry.com/api/v1/resolve?ref=kamiazya/whiteboard/.claude/agents/marketing.md GET https://markdownregistry.com/api/v1/blob/cf4f3e31dc3e33c195ec8574c52e15ec4fb95e56e34aa5cecc3cebc07f0e1d83
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: which agent file does what.
More from kamiazya/whiteboard
Every file in kamiazya/whiteboard