~ / rigs / Dimagious / dashsidian

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.

↗ GitHub ★ 1 MIT updated 8d ago project Claude Code
share on X
ARCHETYPE
Pragmatist
A balanced, no-drama setup: some rules, some tools, nothing extreme.
CONTEXT TAX · EVERY TURN
~4.4k tokens
Moderate · median rig: 2.3k · breakdown
GUARDRAILS
0/5
No committed guardrails · details
Quality 0/100 Guardrails v2

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

copied ✓