philoserf

Re-normalizes MCP connector enable/disable state across all project entries in ~/.claude.json (computer-use on; claude-in-chrome and claude.ai connectors off). Use when project dirs drift off the connector spec and every entry needs fixing at once.

Copy edits prose while preserving voice and register. Use when asked to edit, copy edit, line edit, proofread, revise, polish, tighten, rewrite, or clean up essays, articles, drafts, or fiction. Flags wordiness, passive voice, clichés, hedging, and nominalizations with bracket markup or clean rewrites.

Audits ~/.claude/skills/ for unused entries, duplicate names, missing descriptions, and the longest descriptions. Use when trimming the user-level skill set, asking which skills are unused, finding duplicates, or auditing skill hygiene.

Creates a meeting-minutes file in content/minutes/ with complete frontmatter in Draft state. Use when recording, drafting, or filing minutes for an annual, special, or regular meeting. Computes the dated filename and the correct US Eastern offset for the meeting datetime.

Creates a news post in content/news/ with the section's minimal frontmatter (title, description, date). Use when posting an event recap, announcement, or casual club update. Computes the dated filename and the correct US Eastern offset automatically.

Creates an RONR meeting notice in content/notices/ with complete frontmatter. Use when posting a notice of an annual or special meeting, a motion requiring previous notice, or a bylaw amendment. Computes the dated filename, expires date, and correct US Eastern offset.

Build and deploy the plugin to the local Obsidian vault. Use when testing locally, copying to vault, or installing a dev build.

Orchestrate the full release preparation sequence — version bump, changelog, walkthrough, and validation

Use when auditing this agent-memory vault for stale entries, broken or asymmetric wikilinks, missing cluster cross-links, or INDEX.md drift; or when periodic vault maintenance is requested ("audit", "clean up", "review the wiki", "what should we do with this").

Detects drift between implementation and spec before committing. Use when about to commit, after implementation, or asking "is the spec accurate?" Compares staged diffs against specs to surface and reconcile decisions.