agentleFS
Cassius2584Cassius2584/claude-uni-workspace/.claude/skills/setup-obsidian/SKILL.md

setup-obsidian

Skill5 starsChanged 25 days agoMITView on GitHub

Set up Obsidian for this workspace so it looks and works as intended. Lists the community plugins (Spaced Repetition, Full Calendar Remastered, Style Settings, Homepage, Advanced URI) and the AnuPpuccin theme and offers to install them in one approved batch (or the student clicks Install for each), then applies the dashboard styling, theme preset, calendar settings and a colour-coded graph (plus a local-graph sidebar) from this skill's assets, and makes HOME the first page. Use when the student says "set up Obsidian", "make Obsidian look nice", "style my vault", after setup-year, when HOME looks like plain callouts (pencil icons, no gradient header), or when they ask to make the graph view nicer or more useful.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 2 are distinctive, and 8 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.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If you can run commands, run python3 .claude/skills/setup-obsidian/scripts/install_plugins.py plan from the workspace root.

    line 55
  2. Very specific:

    Yes: ask them to quit Obsidian (it can overwrite community-plugins.json while it runs), then run install_plugins.py install.

    line 59
  3. Distinctive:

    Never install a single item outside this list, or a newer source than Obsidian's directory points to.

    line 71
  4. Very specific:

    Check it worked: each plugin has a folder in .obsidian/plugins/<id>/ and is listed in .obsidian/community-plugins.json, and …

    line 72
  5. Very specific:

    Check what's installed (.obsidian/plugins/<id>/manifest.json, .obsidian/themes/, .obsidian/appearance.json), then, backing up each existing …

    line 78
  6. Very specific:

    HOME: if HOME.md isn't at the workspace root, copy projects/_template/HOME.md there.

    line 95
  7. Very specific:

    Graph view: start from assets/graph.json, keeping any colour groups the student already has.

    line 110
  8. Very specific:

    Add them to userIgnoreFilters in .obsidian/app.json (merge, keep existing entries): projects/_template/, tasks/_template/, …

    line 119
  9. Distinctive:

    Ask for a screenshot of HOME.

    line 151
  10. Very specific:

    Every changed file has a .bak next to it.

    line 164

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Set up Obsidian

The workspace is an Obsidian vault. This skill gets it from "plain Markdown" to the intended look: a card-style HOME dashboard, the Catppuccin-based AnuPpuccin theme, and the plugins the other skills rely on.

Assets (in this skill's folder):

  • assets/dashboard.css: the card layout for dashboard pages (HOME, DEADLINES, TASKS, the tracker, module pages, the timetable). It only affects notes with cssclasses: dashboard. It uses the theme's Catppuccin colours and falls back to fixed colours in any other theme.
  • assets/homepage.json: Homepage plugin preset (open HOME on startup, in Reading view).
  • assets/hide-template-files.css: hides the template folders, the example module and the repo's own files (README, AGENTS, LICENSE, CLAUDE.md) from the file list, so the vault shows only the student's own notes.
  • assets/graph.json: graph view preset: hides admin notes (timetable blocks, templates, digests, HOME and other hubs) and orphans, tighter layout, arrows, and colour groups for concepts, careers and tasks. Module colours are added per student.
  • assets/local-graph-leaf.json: a Local graph panel for the right sidebar (two links out from the open note).
  • assets/timetable-explorer.css: hides the generated calendar-note folders (timetable/blocks, deadlines, events, archive) in the file list. The calendar still reads them.
  • assets/plugins/calendar-scroll-to-now/: a small local plugin from this workspace (no download). Full Calendar always opens day and week views scrolled to 06:00; this centres them on the current time instead.
  • scripts/install_plugins.py: installs the plugins and theme from Obsidian's community directory (plan, then install).
  • assets/style-settings-anuppuccin.json: the AnuPpuccin preset (Mocha, mauve accent, card layout, depth tabs, floating status bar, rainbow folders, coloured headings, styled tables, custom checkboxes).

Installing is the student's call. Plugins and themes are code that runs inside Obsidian with access to the whole vault. Claude offers to install the list below for them, but only after the student approves the whole batch with every item, its source and its size shown. Otherwise the student clicks Install for each item. Only install items listed in Obsidian's own community directory, and nothing outside the list without asking. Claude writes settings files inside .obsidian/ only after the student says yes, and backs up any file first.

1. Install the plugins and theme

  1. Obsidian installed and the vault open: https://obsidian.md/download, then Open folder as vault → this workspace. Open it once, so the .obsidian/ folder exists.
  2. Turn on community plugins: the student does this, always. Obsidian keeps Restricted mode in its own app storage, not in a vault file, so Claude can't (and mustn't) switch it. Explain it simply: it allows plugins from Obsidian's community directory. Settings → Community plugins → Turn on community plugins. (Or open obsidian://show-plugin?id=homepage: while Restricted mode is on, it lands on that page with the button.)
  3. Show the list and offer to install it. The plugins and theme are:

    ItemidFor
    Spaced Repetitionobsidian-spaced-repetitionflashcards (create-flashcards)
    Full Calendar Remasteredfull-calendar-remasteredtimetable, HOME's week agenda
    Style Settingsobsidian-style-settingsapplies the theme preset
    Homepagehomepageopens HOME on startup
    Advanced URIobsidian-advanced-uriHOME's Open calendar and Flashcards buttons
    AnuPpuccin (theme)AnuPpuccinthe Catppuccin look
    Calendar: scroll to nowbundled in assets/plugins/calendars open at the current time, not 06:00

    If you can run commands, run python3 .claude/skills/setup-obsidian/scripts/install_plugins.py plan from the workspace root. It resolves each item through Obsidian's directory and prints a table with the author, GitHub source, latest version, files and sizes (about 7 MB in all), plus what's already installed. Show that table and ask once: "Install all of these for you?" Then:

    • Yes: ask them to quit Obsidian (it can overwrite community-plugins.json while it runs), then run install_plugins.py install. It downloads exactly the listed files from each latest release, checks every plugin's manifest id, copies the bundled plugin, enables everything in .obsidian/community-plugins.json and sets the theme if none is set, backing up each file to .bak. Then they reopen Obsidian. If Obsidian asks whether to trust the vault's plugins, they choose to trust them.
    • No, or they'd rather click: open each install page (macOS open "<link>", Windows start "" "<link>", Linux xdg-open "<link>"), one at a time, waiting for Install then Enable (theme: Install and use): obsidian://show-plugin?id=<id> for each plugin and obsidian://show-theme?name=AnuPpuccin. Without a shell, give them the links. If a link doesn't open the page (older Obsidian), use Settings → Community plugins → Browse, or Appearance → Themes → Manage, and search by name. The bundled plugin isn't in the directory: copy assets/plugins/calendar-scroll-to-now/ to .obsidian/plugins/, add its id to community-plugins.json, and they enable it under Settings → Community plugins after a reload.
    • Never install a single item outside this list, or a newer source than Obsidian's directory points to.
  4. Check it worked: each plugin has a folder in .obsidian/plugins/<id>/ and is listed in .obsidian/community-plugins.json, and .obsidian/appearance.json has "cssTheme": "AnuPpuccin". Ask them to finish anything that's missing. They can keep another theme if they prefer: the dashboard works with any, and only the preset below is skipped.

2. Apply the settings (after they confirm)

Check what's installed (.obsidian/plugins/<id>/manifest.json, .obsidian/themes/, .obsidian/appearance.json), then, backing up each existing file to <file>.bak first:

  1. Dashboard snippet: copy assets/dashboard.css to .obsidian/snippets/dashboard.css, and add "dashboard" to enabledCssSnippets in .obsidian/appearance.json, keeping existing entries and settings.
  2. Theme preset (only if AnuPpuccin is the theme and Style Settings is installed): if .obsidian/plugins/obsidian-style-settings/data.json doesn't exist, copy the preset there. If it exists, the student has their own settings: ask first, and merge only the keys they want.
  3. Reading view by default: set "defaultViewMode": "preview" in .obsidian/app.json (merge, keep the other keys). Pages open as dashboards; Cmd/Ctrl+E switches a page to editing.
  4. Full Calendar: in .obsidian/plugins/full-calendar-remastered/data.json (it exists once the plugin has been enabled), set "weatherHide": true. Otherwise an unconfigured weather widget fills every day header. (If they'd rather have forecasts, set weatherCity instead, e.g. "Bath".) Also add a Deadlines calendar to calendarSources unless one already points at timetable/deadlines: {"type": "local", "name": "Deadlines", "color": "#ef4444", "id": "local_<next free number>", "directory": "timetable/deadlines", "template": "", "taskCompletionStyle": "datetime"}. Then run python3 .claude/skills/create-study-timetable/scripts/sync_deadlines.py from the workspace root to fill it: each dated assessment shows in red in the calendar's all-day row. Change nothing else.
  5. HOME: if HOME.md isn't at the workspace root, copy projects/_template/HOME.md there. Its Open calendar and Flashcards pills are Advanced URI links (obsidian://adv-uri?commandid=…) that run Full Calendar's and Spaced Repetition's commands. Remove them if those plugins aren't installed. Delete the cards for features they haven't set up, plus header pills pointing at pages that don't exist yet (the note at the bottom of the template lists them), and remove that note.
  6. Homepage plugin (required: without it Obsidian reopens whatever was last open, not HOME). Check it's installed and enabled ("homepage" is in .obsidian/community-plugins.json); if not, send them back to its install link. Then write .obsidian/plugins/homepage/data.json: if it doesn't exist, copy assets/homepage.json; if it does (the plugin writes its own defaults, which point at "Home"), set these keys under homepages["Main Homepage"] from the asset and keep the rest: kind: "File", value: "HOME", openOnStartup: true, openMode, view. HOME.md must exist at the root (step 5). Also turn off Spaced Repetition's note review panel on startup: set "enableNoteReviewPaneOnStartup": false in .obsidian/plugins/obsidian-spaced-repetition/data.json (under settings if that key exists). Otherwise that panel takes focus in the right sidebar as Obsidian starts, and Homepage opens HOME there, leaving the main area empty. Flashcard review (the Flashcards button in the left ribbon) isn't affected.
  7. Graph view: start from assets/graph.json, keeping any colour groups the student already has. Add one colour group per module folder, path:projects/<CODE>, before the careers and tasks groups, using these colours in order (convert the hex to the decimal rgb value): #F76B15, #E54666, #8E4EC6, #3E63DD, #12A594, #46A758, #E2A336, #D6409F, #0090FF, #978365. Drop filters for folders that don't exist. Write it to .obsidian/graph.json.
  8. Tidy the file list: the templates, example module and repo files have to stay (skills copy from the _template/ folders, and git updates them), so hide them rather than delete them. Never delete them.
    • Copy assets/hide-template-files.css to .obsidian/snippets/ and add "hide-template-files" to enabledCssSnippets in appearance.json. This hides them in the file list.
    • Add them to userIgnoreFilters in .obsidian/app.json (merge, keep existing entries): projects/_template/, tasks/_template/, careers/_template/, projects/EXAMPLE-MA30001-linear-algebra/, README.md, AGENTS.md, LICENSE, CLAUDE.md. This hides them from search, the graph and link suggestions.
    • Copy assets/timetable-explorer.css to .obsidian/snippets/ and add "timetable-explorer" to enabledCssSnippets. This hides the hundreds of generated calendar notes under timetable/, so the folder shows just TIMETABLE.md. Tell the student they can see them again by turning off the snippets.
  9. Local graph sidebar: in .obsidian/workspace.json, put the leaf from assets/local-graph-leaf.json (give it a fresh 16-hex-digit id, and copy the module colour groups into its options.colorGroups) first in the right sidebar's tab group, make it the current tab, and set "collapsed": true, so Obsidian opens on just HOME and the graph is one click away. Remove any note (markdown) leaf in the right sidebar: it's a stray copy of HOME. Obsidian re-adds its own panels (Backlinks, Outline) as tabs behind the graph on startup. That's fine, because the graph stays in front. Skip this step if the student would rather keep their sidebar as it is. The sidebar is collapsible (icon at top right).

Then ask them to reload Obsidian: Cmd/Ctrl+P → "Reload app without saving". Plugins read their settings at startup. Warn them not to open those plugins' settings before reloading, or the plugin may save over the file. Obsidian also rewrites workspace.json and graph.json as it runs, so for steps 7–9 either use "Reload app without saving" straight after writing, or ask the student to quit Obsidian first (the safest option).

The graph only becomes useful once notes link by idea rather than by folder. create-flashcards offers concept notes for that (concepts/, one note per theorem, method or proof technique, linked to every module it appears in). Mention it.

3. Calendar sources (the student does this in Full Calendar's settings)

  • Add calendar → Full Note → folder timetable/blocks (once a study timetable exists).
  • The red Deadlines calendar (timetable/deadlines) is already added by step 4. It's generated from the assessment notes, so students change dates there, not by dragging deadlines in the calendar.
  • Add calendar → ICS → their university timetable's subscribe link. It's read-only and refreshes by itself. The link is private, so it goes only into the plugin, never into a note or chat.

4. Check

Ask for a screenshot of HOME. It should show a gradient header with pill links, cards with coloured icon labels, no title or Properties box at the top, and inline tables without toolbars. If it still shows pencil icons, the snippet isn't enabled (Settings → Appearance → CSS snippets → dashboard). Reading view looks best. Then the graph view (Cmd/Ctrl+G): each module in its own colour, and no timetable blocks or orphans. The file list shows no _template folders, example module or README.

Finally, check HOME opens by itself: ask them to quit Obsidian completely and reopen it. ("Reload app" isn't the same as a cold start.) If another note opens, or HOME appears in the right sidebar with an empty main area, check in order: Homepage is enabled (community-plugins.json); its data.json has kind: "File", value: "HOME" and openOnStartup: true; Spaced Repetition's enableNoteReviewPaneOnStartup is false; there's no note (markdown) leaf in the right sidebar of workspace.json; and HOME.md exists at the root.

Undo

Every changed file has a .bak next to it. To remove the look, turn off the snippet and restore the backups.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.