all publishers

benoror

@benoror source repo

50 published skills

  1. ▌
    Pr Description 2 · benoror
    Draft concise PR descriptions from branch context. Use when the user asks for /pr-description, a PR description, pull request summary, or branch change summary — especially when API or client contracts may change.
    165 repo stars
  2. ▌
    Gh Stack 2 · benoror bundle
    Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.
    165 repo stars
  3. ▌
    Show Me 2 · benoror
    Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.
    165 repo stars
  4. ▌
    Show Me · benoror
    Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.
    165 repo stars
  5. ▌
    Product Description · benoror bundle
    Build a "product description" repo for a software product — a set of prose documents describing, from the outside in, what the user sees, what they can do, and exactly what happens when they do it, written from the code and tests, then verified against the running product and triaged into a bug list. Works for any product with a user (canvas editors, web apps, CLIs, chat products, mobile apps). Use when the user asks to "write a product description for X", "describe the user experience of X", "document how X behaves for the user", "make a behavior-spec repo", or wants a feature-by-feature, event-by-event account of an app's behavior rather than API docs. Also use to resume or extend an existing product description repo.
    165 repo stars
  6. ▌
    Qmd · benoror bundle
    Search vault notes by keyword or meaning. Args: <query>. Uses QMD (lex, vec, deep search).
    165 repo stars
  7. ▌
    Defuddle · benoror
    Extract clean markdown content from web pages using Defuddle CLI, removing clutter and navigation to save tokens. Use instead of WebFetch when the user provides a URL to read or analyze, for online documentation, articles, blog posts, or any standard web page.
    165 repo stars
  8. ▌
    Handoff · benoror
    Compact the current conversation into a handoff document for another agent to pick up.
    165 repo stars
  9. ▌
    Grilling · benoror
    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
    165 repo stars
  10. ▌
    Research · benoror
    Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
    165 repo stars
  11. ▌
    Implement · benoror
    Implement a piece of work based on a spec or set of tickets.
    165 repo stars
  12. ▌
    Prototype · benoror bundle
    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
    165 repo stars
  13. ▌
    Wayfinder · benoror
    Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
    165 repo stars
  14. ▌
    To Tickets · benoror
    Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
    165 repo stars
  15. ▌
    Find Skills · benoror
    Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
    165 repo stars
  16. ▌
    Skill Creator · benoror bundle
    Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
    165 repo stars
  17. ▌
    Writing For Agents · benoror bundle
    Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
    165 repo stars
  18. ▌
    Setup Matt Pocock Skills · benoror bundle
    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
    165 repo stars
  19. ▌
    Tdd · benoror bundle
    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
    165 repo stars
  20. ▌
    To Spec · benoror
    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
    165 repo stars
  21. ▌
    Ask Matt · benoror bundle
    Ask which skill or flow fits your situation. A router over the skills in this repo.
    165 repo stars
  22. ▌
    Gh Stack · benoror bundle
    Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.
    165 repo stars
  23. ▌
    Code Review · benoror
    Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
    165 repo stars
  24. ▌
    Claude Handoff · benoror bundle
    Hand the current conversation off to a fresh background agent that picks up the work immediately.
    165 repo stars
  25. ▌
    Pr Description · benoror
    Draft concise PR descriptions from branch context. Use when the user asks for /pr-description, a PR description, pull request summary, or branch change summary — especially when API or client contracts may change.
    165 repo stars
  26. ▌
    Diagnosing Bugs · benoror
    Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
    165 repo stars
  27. ▌
    Resolving Merge Conflicts · benoror
    Use when you need to resolve an in-progress git merge/rebase conflict.
    165 repo stars
  28. ▌
    Improve Codebase Architecture · benoror bundle
    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
    165 repo stars
  29. ▌
    Recap · benoror
    Produce a weekly/date-range recap from emails, Slack, Jira/Confluence, and vault notes. Args: [dates]. Default = this week.
    165 repo stars
  30. ▌
    Commit · benoror
    Stage and commit with flexible intent parsing. Accepts file/folder scope, free-text description, amend, or any combination.
    165 repo stars
  31. ▌
    Meeting · benoror bundle
    Create or wrap meeting notes. Args: {title} [folder=X], wrap <path>, wrap pending [today|this week|dates]. No args = pick from Google Calendar.
    165 repo stars
  32. ▌
    Last 1on1 · benoror
    Show when you last had a 1:1 with each direct report / peer, sorted by recency. Flags people who haven't had one in N weeks. Powered by the OneOnOnes view on Meetings.base.
    165 repo stars
  33. ▌
    Cache Notes · benoror
    Fetch & embed AI transcripts as Obsidian callouts. Args: <path>, all, refresh <path>. Prompts for URLs if empty.
    165 repo stars
  34. ▌
    JSON Canvas · benoror bundle
    Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.
    165 repo stars
  35. ▌
    Note Status · benoror
    Verify meeting notes are fully processed. Args: <path>, [dates], all, pending [dates] [--step=X]. Shows which wrap steps are complete or missing.
    165 repo stars
  36. ▌
    Otter Fetch · benoror bundle
    Fetch Otter.ai transcript data. Sub-skill used by cache-notes and fill-participants when Notes: contains an Otter URL.
    165 repo stars
  37. ▌
    Migrate Tags · benoror
    Migrate body-level #hashtags to frontmatter `tags:` lists so Bases can filter on them. Idempotent — leaves files that already have frontmatter tags alone.
    165 repo stars
  38. ▌
    Obsidian CLI · benoror
    Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, search vault content, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
    165 repo stars
  39. ▌
    People Stubs · benoror
    Batch-create Teams/People/@Name.md stubs from unresolved [[@*]] wikilinks across the vault. Each stub is minimal frontmatter; the user fills team/role/details later.
    165 repo stars
  40. ▌
    Sprint Retro · benoror
    Draft a Sprint Retro by synthesizing scrum dailies, recaps, the sprint planning note, and the prior retro. Args: [sprint number | dates]. No args = infer the current sprint.
    165 repo stars
  41. ▌
    Vault Health · benoror
    Audit the vault for structural issues: unresolved wikilinks, orphan notes, dead-end notes, and Obsidian sync conflicts. Optional --fix flags create stubs or surface fixable issues.
    165 repo stars
  42. ▌
    Followup Todos · benoror
    Extract action items as plain markdown bullets (with confirmation). Args: <path>. No args = run [/note-status pending --step=todos](../note-status/SKILL.md#pending-mode).
    165 repo stars
  43. ▌
    Obsidian Bases · benoror bundle
    Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
    165 repo stars
  44. ▌
    Onboard Person · benoror
    Create or enrich a Teams/People/@Name.md file with metadata pulled from external sources (an ATS for hiring data, a profile source for bio). Replaces manual data entry for newly-hired teammates.
    165 repo stars
  45. ▌
    Workspace Mode · benoror
    Switch between named Obsidian Workspace layouts (interview / scrum / 1-on-1 / recap) for context-appropriate file/pane layouts. Wraps `obsidian workspace`.
    165 repo stars
  46. ▌
    Mail Transcripts · benoror bundle
    Gmail AI transcript notifications → meeting Notes: URLs + mark read. Args: (none). Invoked standalone or as step 1 of /meeting wrap.
    165 repo stars
  47. ▌
    Fill Participants · benoror
    Resolve and fill Participants frontmatter + link unlinked names in body. Args: <path>, all.
    165 repo stars
  48. ▌
    Obsidian Markdown · benoror bundle
    Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
    165 repo stars
  49. ▌
    Organize Meetings · benoror
    Triage Meetings/_inbox/ — move each file to the correct subfolder by finding adjacent/similar notes via qmd, applying learned routing conventions from memory, and confirming with the user.
    165 repo stars
  50. ▌
    Sync Upstream Obsidianos · benoror
    Pull structural updates from upstream ObsidianOS into the local vault.
    165 repo stars