← all publishers

aspiers

@aspiers source repo

Report this profile Claim this profile

• 55 skills
• 0 followers
• last month last updated

1. ▌
   Open In User Browser · aspiers

   Open a URL or local file in the user's regular browser, including live-rendered local Markdown. Use for `/open` or when the user asks to view a target outside the agent browser.
   13 installs
2. ▌
   Git Branch Mixer · aspiers

   Manage git branch mixes and run mixdowns using ggmx and ggmxd. Use when the user says things like "add this branch to the mix", "remove a branch from the mix", "show the mix", "mix down the branches", or "run a mixdown".
   12 installs
3. ▌
   Obs Management · aspiers bundle

   Manage Open Build Service (OBS) projects. Use when creating, building, testing, debugging, publishing, or installing packages for home:aspiers.
   14 installs
4. ▌
   Epds Login · aspiers bundle

   Implement AT Protocol OAuth login against an ePDS instance. Covers two flows — Flow 1 (email-first, hand-rolled PAR/DPoP) and Flow 2 (via @atproto/oauth-client-node, accepting no hint / handle / DID). Use when building passwordless OTP login, configuring client metadata (confidential vs public), or integrating NodeOAuthClient.
   3 installs
5. ▌
   Writing Changesets · aspiers

   Create changeset files for changes to ePDS that affect end users, client app developers, or operators. Use when adding features, changing configuration, altering OAuth flows, or any change a downstream consumer needs to adapt to.
   10 installs
6. ▌
   Managing Herdr Plugins · aspiers bundle

   Installs, audits, forks, develops, links, updates, and removes Herdr plugins. Use whenever working with Herdr plugins, herdr-plugin.toml, the Herdr marketplace, local plugin forks, plugin PRs, or switching Herdr from an upstream plugin to a local checkout.
   12 installs
7. ▌
   Project Initialization · aspiers

   Establish concise, cross-agent project instructions from repository evidence. Use when initializing or repairing AGENTS.md, CLAUDE.md, related discovery links, or project-specific agent guidance.
   11 installs
8. ▌
   Agent Command Authoring · aspiers

   Create Claude Code slash commands, OpenCode command files, and Pi prompt templates that delegate to the right subagent or skill. Use when creating new commands or refactoring existing ones to follow platform conventions.
   18 installs
9. ▌
   Beads Parallel Grinding · aspiers

   Grind through ready beads in priority order by running several issues at once, each in its own isolated git worktree managed by worktrunk (`wt`), then merging the finished branches back one at a time. Use when asked to work the beads queue in parallel, to run N issues concurrently, or when a serial grind is too slow and the ready issues are independent.
   16 installs
10. ▌
    Comparing Open Source Projects · aspiers bundle

    Researches and compares free and open source software projects in a supplied domain, using either user-named candidates or a discovered shortlist. Use when evaluating FOSS alternatives, comparing GitHub popularity, maintenance, licences, domain fit, trade-offs, or producing a linked HTML comparison report.
    16 installs
11. ▌
    Code Linting · aspiers

    Discover and run the linters and format checks relevant to changed code. Use after code edits or when the user asks for lint, formatting, or static-analysis validation.
    14 installs
12. ▌
    Editorconfig · aspiers

    Generates a minimal .editorconfig with sensible defaults for a repository. Use when starting work in a new repository, when a project has no .editorconfig, or when the user asks to add or standardise editor and formatting settings.
    13 installs
13. ▌
    Linear Ready · aspiers bundle

    Find Linear issues ready for an AI agent to pick up. Equivalent of `bd ready` for Linear workflows. Use when starting a session to find claimable work, or when asked "what's next" or "find work".
    9 installs
14. ▌
    Test Running · aspiers

    Discover and run tests that provide meaningful evidence for a code change. Use after implementation, before handoff or commit, or when the user asks to validate behavior.
    13 installs
15. ▌
    Triaging Prs · aspiers bundle

    Scan every open pull request in a GitHub repository, filter to the ones that are genuinely mergeable now, and report a compact verdict with a suggested merge order. Use when the user asks which PRs can be merged, wants an open-PR backlog triaged or reviewed in bulk, asks why a PR is blocked, or wants to clear a queue of stale or bot-reviewed PRs.
    9 installs
16. ▌
    Xero Browser · aspiers

    General Xero browser automation notes. Use when automating any Xero page with agent-browser — covers non-standard UI patterns, waiting, and dropdown menus.
    13 installs
17. ▌
    Plan To Beads · aspiers

    Decompose an approved implementation plan into self-contained beads issues with zero guesswork. Use when breaking down a plan file into actionable beads tasks.
    13 installs
18. ▌
    Beads Grinding · aspiers

    Grind through ready beads serially in priority order, one at a time in the current worktree, without stopping between issues. Use when asked to work the beads queue, grind the backlog, keep working through ready issues, or make unattended progress overnight. For concurrent worktrees instead, use beads-parallel-grinding.
    17 installs
19. ▌
    Code Reviewing · aspiers

    Review changed code for correctness, security, maintainability, and verification gaps. Use when code is ready for independent review or before handoff, staging, or merge.
    10 installs
20. ▌
    Describing Prs · aspiers bundle

    Generates a pull request description for the current branch and writes it as Markdown to .git/magit/posts/new-pullreq for magit-forge. Use when the user asks for a PR description, PR summary, or write-up of what a branch changes, or is preparing to open a pull request.
    12 installs
21. ▌
    Git Rebase All · aspiers

    Rebases every local branch of a fork onto a moved upstream, flags the ones upstream has superseded, and rebuilds the mixdown branch that combines them. Use after fetching a fork's upstream and finding it has advanced far, been force-pushed, or rewritten its history; when several stacked or sibling branches all need bringing forward at once; when a branch was cut from a mixdown and now carries merge commits it should not have; or when asked to rebase all branches, re-mix, or bring a whole worktree set up to date.
    12 installs
22. ▌
    Plan To Linear · aspiers

    Decompose an approved implementation plan into self-contained Linear issues with zero guesswork. Use when breaking down a plan into actionable Linear tasks via the MCP server.
    14 installs
23. ▌
    Prp Generation · aspiers

    Generate a Product Requirements Prompt (PRP) from a feature description. Use when starting work on a new feature.
    13 installs
24. ▌
    Hubdoc Reviewer · aspiers bundle

    Review all unreviewed documents in Hubdoc. Use when reviewing, processing or publishing Hubdoc receipts and bills.
    14 installs
25. ▌
    Skill Authoring · aspiers

    Create and maintain agent skills with concise trigger metadata, judgement-aware guidance, progressive disclosure, and tested interfaces. Use when adding, refactoring, reviewing, or troubleshooting skills and their bundled scripts or references.
    14 installs
26. ▌
    Task Generation · aspiers

    Turns an existing Product Requirements Prompt at .ai/[feature]/prp.md into a step-by-step task list of parent tasks and sub-tasks, saved to .ai/[feature]/tasks.md and committed. Use when a PRP is ready to be broken down into implementable work, or when planning how a feature will be built before any implementation starts. To write the PRP itself first, use prp- generation.
    15 installs
27. ▌
    Watching CI Runs · aspiers bundle

    Watch a CI run's jobs to completion without idling or hand-writing a poll loop. Use when a dispatched or pushed build takes minutes to finish and its per-job results decide the next step.
    15 installs
28. ▌
    Checking Upstream · aspiers

    Checks the canonical upstream issue tracker and open pull requests, merge requests, or equivalent change queues for existing reports, discussion, or work on a problem just discussed. Use before diagnosing, fixing, or reporting an apparent open-source problem to avoid duplicate effort and missed context.
    16 installs
29. ▌
    Github Attachments · aspiers

    Upload images and files to GitHub PRs, issues, and comments so GitHub hosts them instead of committing binaries to the repository. Use when adding screenshots to a PR or issue body, replacing committed screenshots or raw.githubusercontent.com links with hosted attachments, or when `gh` appears to offer no way to attach a file.
    15 installs
30. ▌
    Subagent Authoring · aspiers

    Create subagent definitions for Claude Code and OpenCode that delegate to skills. Use when creating new subagents or refactoring existing ones to follow the delegation pattern.
    17 installs
31. ▌
    Task Orchestration · aspiers

    Runs the full implement-and-commit loop over a task list — selects the next incomplete sub-task, implements it, runs linters and tests, marks it done, commits, and repeats until the list is finished. Use when asked to work through a feature's task list at .ai/[feature]/tasks.md unattended, or to keep going until every sub-task is complete. For a single sub-task with no commit, use task-implementation; to stop for approval between each one, use iterative-development.
    14 installs
32. ▌
    Agent Browser Local · aspiers bundle

    Applies local reliability, viewport, tab-safety, stale-ref, widget, and browser-boundary lessons to every agent-browser automation. Use alongside the upstream agent-browser skill whenever navigating, clicking, filling, testing, extracting, taking screenshots, or debugging any website with agent-browser.
    14 installs
33. ▌
    Incremental Commits · aspiers

    Plan dependency-aware atomic commits for changes that span multiple logical concerns. Use when a refactor, feature, or API change would benefit from reviewable, independently meaningful commit boundaries.
    12 installs
34. ▌
    Submitting Upstream · aspiers

    Prepare and publish upstream issues, feature requests, discussions, pull or merge requests, and patch submissions in the channel the canonical project expects. Use when reporting a problem upstream, requesting a feature, contributing a change, or asking to submit upstream.
    16 installs
35. ▌
    Task Implementation · aspiers

    Implements one numbered sub-task from a task list at .ai/[feature]/tasks.md, running linters and tests, without staging, committing, or marking the task complete. Use when asked to carry out a specific sub-task by number, or as the inner step of a larger loop that handles commits separately. For the full loop including commits, use task-orchestration.
    12 installs
36. ▌
    Allow Agent Commands · aspiers

    Adds or changes allowed commands in AI agent permission configs for OpenCode and Claude Code. Use when a command needs adding to an agent's allow list, when permission settings for existing commands need changing, when setting up a new AI tool that requires command permissions, or when the user asks to stop being prompted for a particular command.
    18 installs
37. ▌
    Beads Best Practices · aspiers

    Applies reusable Beads writing and update practices in every context. Use whenever reading, creating, updating, commenting on, closing, superseding, or handing off Beads issues, including alongside beads, beads-solo, and plan-to-beads workflows.
    15 installs
38. ▌
    Beads Blocker Review · aspiers bundle

    Review every Beads issue waiting on a person, one at a time, using the interactive questionnaire UI rather than plain-text prompts. Use when asked to go through blockers, clear the human queue, answer beads waiting on the user, triage `bd human list`, or unblock agent work that needs a decision.
    17 installs
39. ▌
    Code Refactoring Dry · aspiers

    Evaluate repeated code and consolidate duplication when a shared abstraction improves correctness or maintenance. Use after introducing similar logic or when repeated changes reveal a missing source of truth.
    9 installs
40. ▌
    Managing Pi Packages · aspiers bundle

    Manages Pi packages across their lifecycle: discovers, audits, installs, upgrades, removes, enables, disables, filters, and configures extensions, skills, prompts, and themes from npm, Git, or local sources. Use before any Pi package install or upgrade, when reviewing available updates, changing package activation or configuration, or maintaining the package inventory.
    8 installs
41. ▌
    Pr Comment Resolving · aspiers

    Find and address all unresolved GitHub PR review comments on the current branch's pull request. Use when the user asks to resolve, address, respond to, or reply to PR review feedback — whether from humans, CodeRabbit, Copilot, Claude Code reviewer, or any other source. Triggers on "/rr", "resolve review comments", "address PR feedback", "reply to review threads", "deal with CodeRabbit", etc.
    12 installs
42. ▌
    Slow Command Running · aspiers

    Preserve output from expensive one-shot commands for monitoring and later analysis. Use when rerunning a build, API query, CI inspection, or diagnostic would be costly and a managed background process is not the better interface.
    16 installs
43. ▌
    Documentation Updates · aspiers

    Capture durable project or workflow knowledge discovered during work. Use when a mistake, hidden constraint, repeated question, or changed behavior reveals a documentation gap.
    12 installs
44. ▌
    Git Branch Management · aspiers

    Structures git branches for upstream submission — keeps unrelated changes on separate branches, isolates each in its own worktrunk worktree, records dependencies with git-machete, and recombines them into a temporary mixdown branch for local testing. Use when starting work in a fork, clone, or third- party checkout; when choosing what a new branch should be based on; when a branch is growing a second unrelated concern; when deciding whether to stack branches or keep them independent; when preparing a change for a pull request or patch submission; or when a local build needs several in-progress branches combined.
    14 installs
45. ▌
    Iterative Development · aspiers

    Implements sub-tasks from a task list at .ai/[feature]/tasks.md strictly one at a time, stopping after each to ask the user before starting the next, and keeping the task list and Relevant Files section current. Use when the user wants to review or approve each sub-task before work continues, rather than letting the agent run the list unattended with task-orchestration.
    12 installs
46. ▌
    Agent Browser Viewport · aspiers bundle

    Size the agent-browser Chromium window to fill its current screen, leaving a configurable bottom margin for the desktop panel. Use before any agent-browser automation that needs the full screen visible without elements overlapping or scrolling off (e.g. Xero, dense web apps).
    15 installs
47. ▌
    Code Refactoring Small · aspiers

    Refactor code units whose size or mixed responsibilities impede understanding, testing, or change. Use when recent work makes a function, class, or module materially harder to reason about.
    12 installs
48. ▌
    Sq · aspiers

    Summarises the current session's status so a human can see where things stand and what happens next. Use when the user invokes `/sq`, asks for the status quo, session status, a catch-up, recap, or reminder where things got to, regardless of how much previous output there was.
    12 installs
49. ▌
    Beads · aspiers bundle

    Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.
    14 installs
50. ▌
    Safe Rm · aspiers

    Deletes files and directories through a wrapper that avoids the usual per- command permission prompt. Use whenever files or directories need removing — clearing build artifacts or temporary files, or dropping obsolete files and directories during a refactor.
    13 installs
51. ▌
    Xero MCP · aspiers bundle

    Use the Xero MCP server — obtain/refresh OAuth2 bearer tokens, troubleshoot authentication, and pick up other operational notes for working with Xero MCP tools. Use when Xero MCP tools fail with authentication errors, when the bearer token has expired (tokens last ~30 min), before starting any Xero workflow, or for general guidance on Xero MCP usage.
    15 installs
52. ▌
    Beads Solo · aspiers bundle

    Enforces Beads policy for a repository maintained initially by one owner, granting issue-management and commit authority while requiring explicit permission for Git pushes and Dolt sync or push operations. Use when the user asks to enroll, repair, or operate a solo-maintainer Beads workspace, and when working with Beads in a repository that may carry a beads-solo enrollment.
    13 installs
53. ▌
    Git Commit · aspiers

    Review staged changes and create atomic Git commits whose messages match repository conventions. Use when the user asks to commit, write a commit message, or finalize already staged work.
    15 installs
54. ▌
    Git Staging · aspiers bundle

    Stage whole files, selected hunks, or selected lines in Git without interactive prompts. Use when preparing an exact commit boundary while preserving unrelated working-tree changes.
    13 installs
55. ▌
    XLSX To CSV · aspiers

    Converts XLSX spreadsheets, including multi-sheet workbooks, into CSV files that can be read and grepped directly. Use whenever an .xlsx report needs processing — exports from Xero, Cryptio, bank statements, or any tool that delivers spreadsheet output.
    17 installs