Radin show
🐀 the agentic stack for those who have to save tokens
npx -y skills add shortcuts/radin --skill radin-showAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 19 days oldThe repository was created 19 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Print the current project's BACKLOG.md to the terminal. Use for /radin-show, "show me the backlog", "what's in the backlog", "list backlog items", "print BACKLOG.md".
SKILL.md
1.9 KB, 450 tokens by cl100k_base, as published. Nobody here has run it
Show Backlog
Print the current project's BACKLOG.md as-is. Read-only — no other radin
skill/agent does this; radin-record/radin-review write to it,
radin-plan/radin-execute consume it, this just displays it.
Step 1: Resolve project namespace, locate BACKLOG_FILE
All radin state for a project lives inside that project's repo, in
.claude/.radin/ at the repo root (example: repo /Users/x/proj →
/Users/x/proj/.claude/.radin/BACKLOG.md). Do not compute this path
yourself — run the shared namespace-resolution script and read REPO_ROOT,
NAMESPACE_DIR, BACKLOG_FILE from its output in the same Bash call
(shell state doesn't persist between separate calls):
source <(bash "$HOME/.claude/radin-lib/radin-namespace.sh" | sed 's/^/export /')
test -s "$BACKLOG_FILE" && cat "$BACKLOG_FILE" || echo MISSING
Step 2: Show it
Output was MISSING: tell the user this project has no backlog yet and
point them at radin-record or radin-review to start one. Don't create an
empty file.
Output was the file contents: print them to the user as-is — no
summarizing, reordering, or filtering. If the user's request narrowed scope
(e.g. "show me the fix items", "just the open bugs"), filter to the matching
## <category> section(s) instead of the whole file, but default to the
whole file when they didn't ask for a subset.
Guardrails
- Read-only — never writes to
$BACKLOG_FILEor creates it if missing. - No summarizing/reordering/filtering unless the user's request narrowed scope.
Output
Full contents of $BACKLOG_FILE (or the matching ## <category>
section(s) if scope was narrowed), printed as-is.
</content>
What ships with it: 1 file
127 B alongside SKILL.md
agents/
- openai.yaml127 B