philoserf
38 verified skills456 total stars
skills/flowershow-cli
Publishes and manages Flowershow sites with the `fl` CLI (the Go-based successor to the deprecated `@flowershow/publish` npm package). Use when publishing a note or folder to Flowershow, syncing updates to an existing site, managing auth, listing or deleting sites, or installing/upgrading the CLI.
tools12
skills/typescript-quality-gate
Runs TypeScript/JavaScript code quality checks. Use when checking TypeScript or JavaScript quality, linting, running tests, validating TypeScript code, or running TS/JS checks. Covers formatting and linting with biome, type checking with tsc, and test execution with bun test.
development12
skills/session-review
Wraps up a session with two outputs — a sweep into the auto-memory system to preserve reusable insights for future Claude sessions, and a human-readable recap saved to the Obsidian notes vault. Use for retrospectives, debriefs, post-mortems, or end-of-session reflection.
tools12
skills/cc-release-review
Reviews Claude Code release notes and recommends config updates. Use when a new Claude Code version is released, after running /release-notes, after upgrading Claude Code, when asking "what changed", "what should I update", "review the changelog", "version bump", or "review the latest release". Covers settings.json, hooks, permissions, rules, skills, and CLAUDE.md.
development12
skills/obsidian-cli
Interacts with Obsidian vaults via the Obsidian CLI to read, create, and manage notes, tasks, properties, tags, bookmarks, and templates. Use when working with an Obsidian vault from the command line, adding to daily notes, querying by tag or link, checking sync status, or developing and debugging Obsidian plugins and themes.
tools12
skill-cleaner
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.
testing12
skills/refactor-clean
Structured refactoring with smell detection, severity classification, and before/after metrics. Use when code needs deep structural analysis — decomposing large classes, resolving SOLID violations, eliminating duplication across modules, or reducing cyclomatic complexity. Presents a prioritized plan for approval before making changes. Not for lightweight post-edit polish.
development12
skills/obsidian-release
Executes the final release workflow for Obsidian plugins after obsidian-release-check passes. Use when tagging a release, publishing a version, or shipping an Obsidian plugin. Uses the prep-PR pattern — version bump, CHANGELOG, and walkthrough land in one reviewable PR; tag is applied to the merged commit.
tools12
skills/let-fate-decide
Draws 4 Tarot cards using os.urandom() to inject entropy into planning. Use when prompts are vague, the user says 'let fate decide', makes Yu-Gi-Oh references, demonstrates indifference about approach, or multiple approaches are equally valid. Interprets the spread to generate actionable next steps from randomized input.
testing12
skills/python-quality-gate
Runs Python code quality checks. Use when checking Python quality, linting, type checking, running tests, validating Python code, or running python checks. Covers formatting and linting with ruff, type checking with mypy, and test execution with pytest.
development12
skills/use-trueup
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.
testing12
skills/vc-sync
Syncs local repository with remote. Use when syncing repo, pulling latest, refreshing branches, updating from remote, or cleaning up after merging PRs. Switches to main, pulls latest, and prunes merged branches.
testing12
skills/writing-skills
Scaffolds new skills using Anthropic's skill-creator with local conventions overlaid — naming prefixes, third-person description voice, 500-line target, rename protocol. Use when creating, renaming, or restructuring a skill in this repository.
data-ai12
skills/pre-release-obsidian-plugin
Validates a project is ready to tag and ship. Use when tagging a release, cutting a version, shipping a package, or asking "are we ready to release?" Checks repo hygiene, CI status, docs, version sync, and build verification. Optimized for Obsidian plugins with fallback detection for other project types.
tools12
skills/last30days
Researches any topic using sources tailored to the query — places (local papers, Ground News, city .gov), consumer products (Wirecutter, Serious Eats, Reddit, owner forums), tech/software (official changelogs, GitHub, awesome-lists), medical (PubMed, Cochrane, clinical guidelines), sports (ESPN, SBN blogs, team officials, ISW-style trackers), geopolitics (wire services, think tanks, credentialed analysts), and general trends (Reddit, X, YouTube, HN). Use this skill whenever the user mentions a place, product, person, team, event, a specific app/tool/library, a medical condition or drug, a sports matchup, current news, 'best X' recommendations, 'what's happening with Y,' 'prompts for Z,' or any topic where last-30-days context matters — even if they don't explicitly ask for research. Produces dated synthesis grounded in what sources actually say.
tools12
skills/brainstorming
Explores user intent, requirements, and design through conversational dig-and-advise before implementation. Use when starting creative work — features, components, architecture — where the problem space is not yet well-defined. Produces an approved design that lives in the conversation, not a committed artifact.
data-ai12
skills/md-audit
Audits and improves CLAUDE.md files by scanning repositories. Use when maintaining CLAUDE.md files, optimizing project instructions, or reviewing what project instructions should contain. Evaluates quality against templates, outputs scored reports, and applies targeted updates.
testing12
skills/walkthrough
Reads source code and produces a linear, executable walkthrough document. Use when explaining how code works, creating code walkthroughs, onboarding to a project, or giving a code tour. Generates structured showboat documents with annotated code paths.
development12
skills/diff-review
Runs an iterative review-and-fix loop on a git diff. Use when reviewing a staged or branch diff and fixing findings in place — presents findings by severity, lets you choose which to fix, applies fixes, and re-reviews. Max 3 iterations.
tools12
skills/cc-review
Audits Claude Code skills, hooks, agents, and rules in a single pass — structural lint, quality scoring (1-5 across 6 weighted dimensions), and prioritized improvement recommendations. Use when reviewing, auditing, scoring, linting, improving, or validating any customization. Produces one sectioned report with pass/fail checks, per-dimension scores, weighted total, quality tier, and P1-P5 action items.
development12
skills/code-audit
Reviews a codebase for bugs, design issues, and code cleanliness problems with specific file paths and line numbers. Use when auditing code quality, finding bugs, doing a code review, finding problems, or reviewing a project for issues. Creates issue files in `.issues/` directory.
development12
editor
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.
tools12
skills/tech-debt
Identifies, classifies, and prioritizes technical debt. Use when auditing technical debt, assessing code quality, analyzing maintenance burden, or asking what's slowing us down. Produces categorized inventory with severity rankings, remediation roadmap, and fix recommendations.
development12
skills/release-obsidian-plugin
Executes the final release workflow for Obsidian plugins after pre-release-obsidian-plugin checks pass. Use when tagging a release, publishing a version, or shipping an Obsidian plugin. Bumps version via bun run script, creates git tag, pushes to trigger GitHub Actions, and updates GitHub release notes from CHANGELOG.md.
tools12
skills/use-discipline
Primes the conversation for deep, not-yet-well-defined work by framing the arc — problem framing, brainstorming, planning, execution under rules, review via existing skills. Takes an optional topic argument to seed the problem space. Use to opt into disciplined multi-phase work rather than letting ceremony be always-on.
testing12
skills/writing-plans
Produces a bite-sized implementation plan from an approved design. Use after brainstorming or when ready to execute a multi-step task. Writes the plan to ~/.claude/scratch/plans/YYYY-MM-DD-<topic>.md as working state — never committed — and loads it back when execution starts.
documentation12
graphify
any input (code, docs, papers, images) - knowledge graph - clustered communities - HTML + JSON + audit report
development12
skills/bash-quality-gate
Runs shell script quality checks. Use when checking shell script quality, linting bash code, or validating scripts. Covers formatting with shfmt, static analysis with shellcheck, and portability checks.
development12
skills/cc-setup-recommender
Analyzes a codebase and recommends Claude Code automations. Use when asking for automation recommendations, what automations to add, optimizing or configuring Claude Code setup, or setting up Claude Code for a new project. Covers hooks, subagents, skills, plugins, and MCP servers.
tools12
skills/fix-issue
Plans, implements, reviews, and ships a fix for a GitHub issue. Use when fixing an issue, resolving a bug report, implementing a feature request, or closing a ticket. Handles fork workflows, upstream detection, branch creation, and PR submission.
business12
skills/hugo-cli
Translates plain-English requests about a Hugo static site into correct `hugo` CLI invocations so the user never has to know the flags. Use whenever the user is working in a Hugo project (hugo.yaml / hugo.toml / hugo.json present), mentions Hugo by name, asks to build, preview, serve, deploy, or scaffold a site, asks to create new posts or pages, wants to inspect drafts/future/expired content, or is debugging a Hugo build — even if they never type the word "hugo".
tools12
skills/vc-ship
Automates git commit organization and history cleanup. Use when staging and organizing uncommitted changes into atomic commits, cleaning messy commit history, or formatting commit messages. Not for deciding how to integrate a completed branch.
development12
skills/go-quality-gate
Runs Go code quality checks. Use when checking Go code quality, linting, running checks, validating Go code, or running go checks. Covers formatting with gofumpt, static analysis with go vet, and test execution with go test.
development12
skills/md-capture
Improves CLAUDE.md by analyzing conversation patterns. Use when Claude keeps repeating a mistake, when teaching a new preference, or when consolidating guidance from repeated instructions. Captures recurring corrections and style preferences into project instructions.
tools12
skills/claudemd-capture
Improves CLAUDE.md by analyzing conversation patterns. Use when Claude keeps repeating a mistake, when teaching a new preference, or when consolidating guidance from repeated instructions. Captures recurring corrections and style preferences into project instructions.
tools12
skills/deps-audit
Audits project dependencies for vulnerabilities, outdated packages, and license issues. Use when checking dependency health, running security audits, or reviewing package versions. Covers native audit tools, version freshness, and license compliance.
tools12
skills/claudemd-audit
Audits and improves CLAUDE.md files by scanning repositories. Use when maintaining CLAUDE.md files, optimizing project instructions, or reviewing what project instructions should contain. Evaluates quality against templates, outputs scored reports, and applies targeted updates.
testing12
skills/obsidian-release-check
Validates an Obsidian plugin is ready to tag and ship. Use when tagging a release, cutting a version, publishing or shipping a plugin, running a pre-release check, or asking "are we ready to release?" Checks repo hygiene, CI status, docs, version sync, and build verification.
tools12