Dimagious/dashsidian
Describe the dashboard you want, your AI agent builds it in an Obsidian note. Charts, streaks, heatmaps and goals from note properties, as plain YAML. No JavaScript, no Dataview.
ARCHETYPE
Pragmatist
A balanced, no-drama setup: some rules, some tools, nothing extreme.
Copy this rig
# review before running: this installs third-party code
$ npx degit Dimagious/dashsidian/.claude ./rig-dashsidian # inspect, then merge into .claude/ MCP servers are added to Claude Code at local scope; env vars are shown as YOUR_… placeholders — we never store values. Files are fetched with degit into a separate folder so you can review before merging.
$ npx degit Dimagious/dashsidian/.claude/skills/release-bump .claude/skills/release-bump $ npx degit Dimagious/dashsidian/.claude/skills/tech-writer .claude/skills/tech-writer
$ curl -fsSL --create-dirs -o .claude/agents/checker.md https://raw.githubusercontent.com/Dimagious/dashsidian/master/.claude/agents/checker.md $ curl -fsSL --create-dirs -o .claude/agents/maker.md https://raw.githubusercontent.com/Dimagious/dashsidian/master/.claude/agents/maker.md
This rig commits no guardrails. Here is the community baseline instead — the deny/ask rules most often found across all 16.2k rigs:
{
"permissions": {
"deny": [
"Read(./.env)",
"Read(./.env.*)",
"Read(**/.env)",
"Read(~/.ssh/**)",
"Bash(git push --force:*)",
"Read(**/*.pem)",
"Read(.env)",
"Read(~/.aws/**)",
"Read(**/*.key)",
"Read(**/.env.*)",
"Bash(git push --force*)",
"Bash(rm -rf:*)",
"Bash(rm -rf *)",
"Bash(sudo *)",
"Bash(sudo:*)",
"Bash(rm -rf /)",
"Bash(git push -f:*)",
"Read(.env.*)",
"Bash(git reset --hard*)",
"Bash(rm -rf /*)"
],
"ask": [
"Bash(git push:*)",
"Bash(git push *)",
"Bash(gh pr merge *)",
"Bash(git commit:*)",
"Bash(rm *)",
"Bash(gh pr merge:*)",
"Bash(gh pr create *)",
"Bash(git reset --hard:*)",
"Bash(npm publish:*)",
"Bash(git rebase *)"
]
}
} Skills (2)
Subagents (2)
| checker model: fable | Review agent (Fable). Use after the maker finishes to adversarially review the working-tree diff: correctness, repo conventions (pure core, schema as the single source of keys, i18n), user-facing outp |
| maker model: claude-opus-5-5 | Implementation agent (Opus 5.5). Use to write code for a task that has an agreed scope/plan: TypeScript, tests, styles, catalogs. It implements only; review is done separately by the checker. |
Similar rigs
reviewgate-dev/claude-review-gate
Review gate for Claude Code subagents: fresh reviewer, ship/fix/hold verdict, capped fix loop. Plain markdown, MIT.
Minimalist 227 tok · · Q0
MSergW/agent-harness-template
Ready-made harness for AI coding agents (Claude Code, Codex, Copilot): rules, state, checks, diff review · Готовий харнес для AI-агентів: правила, стан, перевірки, рев'ю
Fort Knox 4.2k tok · · Q42
AlexGavrilov939/spec-dna
Catch the changes that break your Markdown specs (edited accepted decisions, broken links and ids, stale code citations, untested requirements) and give AI coding agents only the sections a file needs. Change lifecycle with requirement delt
Orchestrator 2.0k tok · · Q18
mikeyobrien/ralph-orchestrator
An improved implementation of the Ralph Wiggum technique for autonomous AI agent orchestration
Skill Collector 4.0k tok · · Q0