all publishers

markphelps

@markphelps source repo

30 published skills

  1. ▌
    Vault Lint 2 · markphelps
    Hygiene pass over active notes, ideas, and projects
    6 repo stars
  2. ▌
    Vault Ingest 2 · markphelps
    Use when raw vault captures need classification, routing, relocation, and external-source synthesis from the source inbox into the right vault surfaces
    6 repo stars
  3. ▌
    Vault Compact 2 · markphelps
    Collapse semantically overlapping notes, ideas, and project docs into clearer canonical surfaces while preserving distinct claims, decisions, examples, and source provenance.
    6 repo stars
  4. ▌
    Vault Tracker 2 · markphelps
    Manage PORT object lifecycle through Portent metadata, folder state, and index navigation
    6 repo stars
  5. ▌
    Vault Concepts 2 · markphelps
    Maintain canonical concept pages and surface recurring themes
    6 repo stars
  6. ▌
    Vault Maintain 2 · markphelps
    Weekly bounded maintenance loop across ingestion, hygiene, compaction, lifecycle management, and concepts
    6 repo stars
  7. ▌
    Vault Research 2 · markphelps
    Use when a vault note, idea, project, or topic needs external sources, competitor research, discussion evidence, or market signals
    6 repo stars
  8. ▌
    CLI Design 2 · markphelps
    Design, build, or review command-line interfaces using the Command Line Interface Guidelines from clig.dev. Use this skill whenever the user is creating a new CLI, adding commands/subcommands/flags, designing help text, choosing stdout/stderr/exit-code behavior, adding JSON or plain output modes, improving error messages, making destructive operations safer, or asking whether a CLI feels good, scriptable, discoverable, or Unix-friendly.
    6 repo stars
  9. ▌
    Vault X Bookmarks 2 · markphelps bundle
    Use when X bookmarks need to be captured into raw/sources or existing X bookmark source records need relevance triage
    6 repo stars
  10. ▌
    Oss Marketing 2 · markphelps
    Run a marketing/positioning pass on an open source repo's README and public-facing docs so a developer landing on it for the first time immediately understands what it is, why it exists, and how to use it. Use this whenever the user wants to improve a repo's README, write launch copy for an OSS project, sharpen positioning ("does this README explain what the project does"), prep a repo for a Show HN / Hacker News / Product Hunt / Twitter launch, or asks for an "OSS marketing pass," "README audit," or similar. This is about clarity and conversion (visitor → user → star), not contribution mechanics — for CONTRIBUTING.md, issue templates, CODEOWNERS, or governance docs, that's a different concern.
    6 repo stars
  11. ▌
    Github Pr Fixup 2 · markphelps
    {url} address comments left on a GitHub pull request. Use when a user wants review comments and CI failures fixed on an existing GitHub pull request without opening a new PR.
    6 repo stars
  12. ▌
    Session Log Audit 2 · markphelps
    Audit a project you build with AI agents by mining your own local agent session logs (Claude Code, Pi, Codex) for papercuts, bugs, and design flaws — the friction visible in what you actually typed rather than what the README claims. Use this when the user wants to find rough edges in their own tool or project, asks "what's annoying about X," wants to know why they keep working around their own software, is preparing a UX or DX pass on something they use daily, or wants to turn a week of agent sessions into a ranked fix list. Also trigger for narrower asks that are really this — "why do I keep retyping this command," "audit my CLI's ergonomics," "what should I fix in X this week."
    6 repo stars
  13. ▌
    Oss Repo Readiness 2 · markphelps
    Audit and prepare a GitHub repo for open source release, with a focus on developer experience (DevEx) — the things that determine whether a stranger can go from "found this repo" to "opened a PR" without friction. Use this whenever the user wants to open-source a repo, make a private repo public, do a "pre-launch checklist" or "OSS readiness audit," improve their README/CONTRIBUTING/issue templates, or asks something like "is this repo ready for people to use/contribute to." Also trigger for narrower asks that are really pieces of this — "write a CONTRIBUTING.md," "set up issue templates," "add a CODEOWNERS file" — since those are almost always better done as part of the full readiness pass rather than in isolation.
    6 repo stars
  14. ▌
    Context File Tuneup 2 · markphelps
    Audit, rewrite, and tighten a CLAUDE.md / AGENTS.md file so it actually helps a coding agent instead of bloating its context. Handles repos that use either file name, both names, nested AGENTS.md files, or one file symlinked/aliased to the other. Use this skill whenever the user wants to review, clean up, fix, shrink, restructure, or improve a CLAUDE.md / AGENTS.md file
    6 repo stars
  15. ▌
    Github Self Hosted Runner 2 · markphelps
    Install, register, namespace, verify, or remove one or more GitHub Actions self-hosted runners on a Linux host. Use when a user provides a GitHub repository or organization URL and wants a persistent runner managed by systemd, including adding another repository-specific runner to a machine that already has runners.
    6 repo stars
  16. ▌
    CLI Design · markphelps
    Design, build, or review command-line interfaces using the Command Line Interface Guidelines from clig.dev. Use this skill whenever the user is creating a new CLI, adding commands/subcommands/flags, designing help text, choosing stdout/stderr/exit-code behavior, adding JSON or plain output modes, improving error messages, making destructive operations safer, or asking whether a CLI feels good, scriptable, discoverable, or Unix-friendly.
    6 repo stars
  17. ▌
    Vault Lint · markphelps
    Hygiene pass over active notes, ideas, and projects
    6 repo stars
  18. ▌
    Vault Ingest · markphelps
    Use when raw vault captures need classification, routing, relocation, and external-source synthesis from the source inbox into the right vault surfaces
    6 repo stars
  19. ▌
    Oss Marketing · markphelps
    Run a marketing/positioning pass on an open source repo's README and public-facing docs so a developer landing on it for the first time immediately understands what it is, why it exists, and how to use it. Use this whenever the user wants to improve a repo's README, write launch copy for an OSS project, sharpen positioning ("does this README explain what the project does"), prep a repo for a Show HN / Hacker News / Product Hunt / Twitter launch, or asks for an "OSS marketing pass," "README audit," or similar. This is about clarity and conversion (visitor → user → star), not contribution mechanics — for CONTRIBUTING.md, issue templates, CODEOWNERS, or governance docs, that's a different concern.
    6 repo stars
  20. ▌
    Vault Compact · markphelps
    Collapse semantically overlapping notes, ideas, and project docs into clearer canonical surfaces while preserving distinct claims, decisions, examples, and source provenance.
    6 repo stars
  21. ▌
    Vault Tracker · markphelps
    Manage PORT object lifecycle through Portent metadata, folder state, and index navigation
    6 repo stars
  22. ▌
    Vault Concepts · markphelps
    Maintain canonical concept pages and surface recurring themes
    6 repo stars
  23. ▌
    Vault Maintain · markphelps
    Weekly bounded maintenance loop across ingestion, hygiene, compaction, lifecycle management, and concepts
    6 repo stars
  24. ▌
    Vault Research · markphelps
    Use when a vault note, idea, project, or topic needs external sources, competitor research, discussion evidence, or market signals
    6 repo stars
  25. ▌
    Github Pr Fixup · markphelps
    {url} address comments left on a GitHub pull request. Use when a user wants review comments and CI failures fixed on an existing GitHub pull request without opening a new PR.
    6 repo stars
  26. ▌
    Session Log Audit · markphelps
    Audit a project you build with AI agents by mining your own local agent session logs (Claude Code, Pi, Codex) for papercuts, bugs, and design flaws — the friction visible in what you actually typed rather than what the README claims. Use this when the user wants to find rough edges in their own tool or project, asks "what's annoying about X," wants to know why they keep working around their own software, is preparing a UX or DX pass on something they use daily, or wants to turn a week of agent sessions into a ranked fix list. Also trigger for narrower asks that are really this — "why do I keep retyping this command," "audit my CLI's ergonomics," "what should I fix in X this week."
    6 repo stars
  27. ▌
    Vault X Bookmarks · markphelps bundle
    Use when X bookmarks need to be captured into raw/sources or existing X bookmark source records need relevance triage
    6 repo stars
  28. ▌
    Oss Repo Readiness · markphelps
    Audit and prepare a GitHub repo for open source release, with a focus on developer experience (DevEx) — the things that determine whether a stranger can go from "found this repo" to "opened a PR" without friction. Use this whenever the user wants to open-source a repo, make a private repo public, do a "pre-launch checklist" or "OSS readiness audit," improve their README/CONTRIBUTING/issue templates, or asks something like "is this repo ready for people to use/contribute to." Also trigger for narrower asks that are really pieces of this — "write a CONTRIBUTING.md," "set up issue templates," "add a CODEOWNERS file" — since those are almost always better done as part of the full readiness pass rather than in isolation.
    6 repo stars
  29. ▌
    Context File Tuneup · markphelps
    Audit, rewrite, and tighten a CLAUDE.md / AGENTS.md file so it actually helps a coding agent instead of bloating its context. Handles repos that use either file name, both names, nested AGENTS.md files, or one file symlinked/aliased to the other. Use this skill whenever the user wants to review, clean up, fix, shrink, restructure, or improve a CLAUDE.md / AGENTS.md file
    6 repo stars
  30. ▌
    Github Self Hosted Runner · markphelps
    Install, register, namespace, verify, or remove one or more GitHub Actions self-hosted runners on a Linux host. Use when a user provides a GitHub repository or organization URL and wants a persistent runner managed by systemd, including adding another repository-specific runner to a machine that already has runners.
    6 repo stars