UrdSkill
CLAUDE.md2 starsChanged 22 days agoMITView on GitHub
This repository exists solely so the author can develop and version the urd skill. The canonical file is skills/urd/SKILL.md — people install it as a Claude Code plugin (or copy that one file into their agent's skill dir). Nothing in this repo (CLAUDE.md, CHANGELOG.md, README.md, CI, etc.) may affect the skill's mechanics. All behavior must be self-contained in skills/urd/SKILL.md. Urd (formerly "BePrecise") is an add-on in the Yggdrasil family: it attaches to the agent, not to the graph, and works…
In this repositoryOne other file it gives its agents.
- urdSkill
The file
We split this CLAUDE.md into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
When bumping version, update the version in all of .claude-plugin/plugin.json, .github/plugin/marketplace.json (plugin entry), …
- Distinctive: line 25
When the user says "bump version":
- Very specific: line 27
Update the comparison links at the bottom of CHANGELOG.md (add the new [X.Y.Z]: …compare/vA.B.C...vX.Y.Z line and point [Unreleased] at the …
- Very specific: line 28
Update the version in .claude-plugin/plugin.json, .github/plugin/marketplace.json (plugin entry), .codex-plugin/plugin.json, …
- Distinctive: line 29
Commit the bump and push to main — that's it.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
UrdSkill
Purpose
This repository exists solely so the author can develop and version the urd skill. The canonical file is skills/urd/SKILL.md — people install it as a Claude Code plugin (or copy that one file into their agent's skill dir). Nothing in this repo (CLAUDE.md, CHANGELOG.md, README.md, CI, etc.) may affect the skill's mechanics. All behavior must be self-contained in skills/urd/SKILL.md.
Urd (formerly "BePrecise") is an add-on in the Yggdrasil family: it attaches to the agent, not to the graph, and works alone. It owns the intent → code stage — when the agent moves from a plan/spec into implementation, it consults the source of truth and asks instead of guessing. The family's core is Jarl (the loop), Yggdrasil (the law: the architecture graph and the rails) and Grain (the survey: the first graph, mined from a repository's own code and history); you start at the step where it hurts. Ratatoskr, Urd and Researcher are the three add-ons beside the core, each with no dependency of its own.
Plugin scaffolding
This repo is installable as a Claude Code plugin and as a GitHub Copilot CLI plugin. Layout:
.claude-plugin/plugin.json— plugin manifest (name, version, description, keywords).versionhere MUST match the latest released version inCHANGELOG.mdand is bumped together with it..claude-plugin/marketplace.json— single-plugin marketplace listing for Claude Code, so the repo can be added via/plugin install urd@urd-marketplace..github/plugin/marketplace.json— single-plugin marketplace listing for GitHub Copilot CLI (Copilot reads this path), so the repo can be added viacopilot plugin marketplace add krzysztofdudek/UrdSkillthencopilot plugin install urd@urd-marketplace. Mirrors the Claude listing but additionally carriesversionand askillsarray (./skills/urd). Its pluginversionMUST be kept in lockstep withplugin.json..codex-plugin/plugin.json— plugin manifest for OpenAI Codex CLI (Codex reads the plugin manifest only from.codex-plugin/). Bundles the skill via"skills": "./skills/"; Codex discovers the marketplace from the existing.claude-plugin/marketplace.json(its legacy-compatible path), so the repo installs viacodex plugin marketplace add krzysztofdudek/UrdSkillthencodex plugin install urd@urd-marketplace. ItsversionMUST be kept in lockstep withplugin.json..cursor-plugin/plugin.json— plugin manifest for Cursor (single-plugin-at-root: manifest at the repo root, no Cursor marketplace file; components are auto-discovered, soskills/urd/is picked up automatically). Installed locally via~/.cursor/plugins/local/or published to the Cursor Marketplace. ItsversionMUST be kept in lockstep withplugin.json.skills/urd/SKILL.md— the canonical skill body. Editing this file IS editing the skill.
When bumping version, update the version in all of .claude-plugin/plugin.json, .github/plugin/marketplace.json (plugin entry), .codex-plugin/plugin.json, .cursor-plugin/plugin.json, and the root plugin.json (the portable Agent Plugins 1.0 manifest Copilot and Codex read first) in lockstep with the CHANGELOG section header.
Versioning
This project uses Semantic Versioning and maintains a CHANGELOG.md following the Keep a Changelog format.
When the user says "bump version":
- Move
[Unreleased]entries inCHANGELOG.mdinto a new version section with today's date - Update the comparison links at the bottom of
CHANGELOG.md(add the new[X.Y.Z]: …compare/vA.B.C...vX.Y.Zline and point[Unreleased]at the new version) - Update the
versionin.claude-plugin/plugin.json,.github/plugin/marketplace.json(plugin entry),.codex-plugin/plugin.json,.cursor-plugin/plugin.json, and the rootplugin.json(the portable Agent Plugins 1.0 manifest Copilot and Codex read first) to match - Commit the bump and push to
main— that's it.
Do not create or push tags manually. The .github/workflows/release.yml workflow runs on every push to main, reads the top version from CHANGELOG.md, and if v<version> does not already exist it creates the tag, pushes it, and publishes a GitHub Release with notes extracted from the matching changelog section.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

