block
- 52 skills
- 0 followers
- 23 hours ago last updated
- ▌ Goosetown Worker · blockAutonomous worker for Goosetown. Executes assigned task immediately without waiting for confirmation. Works in isolation - does not coordinate with other workers. Reports completion in final message.
- ▌ Goosetown Writer · blockSynthesizes scattered research, scratch files, and work logs into durable knowledge artifacts — GUIDES, PLANS, or research syntheses. Reads many sources, produces one coherent document. Writes incrementally with citations and proper frontmatter. Handles supersession.
- ▌ Goosetown Reviewer · blockQuality reviewer for Goosetown. Assesses work against specified criteria, identifies issues, scores quality, and provides actionable feedback. Reviews only - does not fix issues directly.
- ▌ Goosetown Orchestrator · blockCoordinate parallel AI delegates — researchers, workers, writers, reviewers — using goose.
- ▌ Goosetown Researcher Jira · blockSearch Jira issues, sprints, boards, and projects using the Atlassian CLI (acli). Finds tickets, sprint status, project context, and team workload. Returns structured findings with issue keys and links.
- ▌ Goosetown Researcher Arxiv · blockSearch arXiv for academic papers, preprints, and research using the arXiv API. Finds foundational research, state-of-the-art techniques, and academic context. Returns structured findings with links, abstracts, and citations.
- ▌ Goosetown Researcher Beads · blockSearch the local beads (bd) issue tracker for issues, dependencies, epics, blockers, and project status. Finds work items, dependency graphs, stale issues, and team workload. Returns structured findings with issue IDs and citations.
- ▌ Goosetown Researcher Local · blockSearch local GUIDES/, PLANS/, RESEARCH/, and WORK_LOGS/ directories for prior decisions, open questions, risks, and relevant context. Uses CATALOG.md for topic discovery and ripgrep for deep searches. Returns structured findings with citations.
- ▌ Goosetown Researcher Slack · blockSearch Slack messages, channels, and threads using the Slack MCP extension. Finds discussions, decisions, announcements, and team context. Returns structured findings with links and citations.
- ▌ Goosetown Researcher Github · blockSearch GitHub issues, PRs, code, and discussions using the gh CLI. Finds prior decisions, implementation patterns, and maintainer discussions. Returns structured findings with links and citations.
- ▌ Goosetown Researcher Reddit · blockSearch Reddit for community discussions, war stories, and anecdotal evidence using the unauthenticated JSON API. Returns structured findings with links. Treat as anecdotal evidence, not authoritative truth.
- ▌ Goosetown Researcher Stackoverflow · blockSearch Stack Overflow for canonical Q&A, error solutions, and implementation patterns using the Stack Exchange API. Returns structured findings with links and vote counts.
- ▌ Releasing Coplan · blockPublish the coplan-engine gem to RubyGems. Use when releasing a new version, publishing the gem, or bumping the version.
- ▌ Drift · block bundleCompare and diff files, directories, builds, releases, archives, or binaries. Use when the user wants to compare two versions of something, diff two directories or files, analyze what changed between builds or releases, or examine differences in .ipa, .apk, .aar, .jar, .tar.gz, .tar.bz2, Mach-O binaries, plists, or text files.
- ▌
- ▌ Edge Case Finder · block bundleAnalyzes branch changes to find edge cases, error states, and untested user flow paths in UI code. Use when the user says "find edge cases", "what am I missing", "edge cases", "test my flows", "what could go wrong", or wants to harden a feature before shipping.
- ▌ Create App E2e Test · blockCreate app e2e tests for the Goose desktop app using the Tauri app test driver. Use when the user wants to generate, write, or verify UI tests that run against the live app.
- ▌ Trailblaze · block bundleUse when working with Trailblaze — natural-language device control for coding agents across iOS, Android, and web, with replayable `.trail.yaml` files as the artifact. Trigger on mentions of Trailblaze, the `trailblaze` CLI, `.trail.yaml` files, trailmaps, waypoints, or requests to drive / author / debug / run UI tests on iOS / Android / web — including authoring a custom typed scripted tool, composing an agent's tool surface, or writing a trailmap.
- ▌ Devlog · blockWrite or update a devlog entry in the devlog directory. Use when the user asks to write a devlog, record a decision, document what happened, or says "write up what we did".
- ▌ Trailblaze Author · blockUse when turning a captured human demonstration (a Trail Runner demonstration bundle: demo.yaml + actions.ndjson + per-action screenshots and view hierarchies) into a durable, independently runnable Trailblaze trail. Trigger when a prompt hands you a demonstration bundle directory and asks you to author, generate, or produce the trail for it - or to add another platform's recordings to an existing trail from a new demonstration.
- ▌ Trailblaze Validate Oob · blockUse when validating or evaluating Trailblaze's out-of-box (OOB) user experience — does what the `trailblaze` skill claims actually match the real installed CLI? Triggers on requests to "validate the Trailblaze skill", "test the Trailblaze OOB experience", "evaluate Trailblaze UX", "check if the skill matches the CLI", "audit the Trailblaze CLI for new-user friction", or running an OOB regression check after the framework changes.
- ▌ Buzz Handoff · blockRead and hand off Buzz channels or threads in a private agent conversation using the installed Buzz CLI. Use when a user shares a buzz://message URL or Buzz channel UUID, asks to continue Buzz work privately, or explicitly approves a reply back to Buzz.
- ▌ Berd Help · block bundleHelp with Berd the desktop app: how-to, troubleshooting, settings, agents, skills, automations, projects, sessions, providers, connections, feedback, or berdctl. Use for app questions, not harness-specific behavior.
- ▌ Create Pr · blockCreate a GitHub PR from the current branch: handle uncommitted changes, generate a summary, submit via gh CLI, then watch the PR to a ready state — fixing failing checks and addressing review comments. Use when the user says "create PR", "open PR", "submit PR", "push PR", or wants to create a pull request.
- ▌ Berd Monitor · blockRun a long-lived command outside the current Berd turn and wake the owning session with actionable stdout. Use for builds, tests, reviews, deployments, polling, watchers, and other external waits.
- ▌ Assistive UX · blockUse when adding, reviewing, designing, testing, or managing Assistive UX moments in Berd, including discover, suggest, and autoApply guidance, adaptive settings, behavior signals, retirement rules, or changes under src/shared/assistive-ux.
- ▌ Agent Builder · blockCreate, edit, or inspect Berd agents/personas stored as Agent Markdown files with YAML frontmatter under ~/.agents/agents. Use when user needs to manage Berd agents or personas.
- ▌ Skill Builder · blockCreate, edit, or inspect Berd skills stored as skill folders with SKILL.md files. Use when the user wants to build a new skill, update an existing skill, convert a workflow into a reusable skill, or decide whether instructions, scripts, references, or assets belong in a skill.
- ▌ Berd Orchestrator · blockCoordinate work across Berd sessions while keeping one conversation available to the user. Use for a long-lived orchestration session.
- ▌ Berdctl New Command · blockUse when adding, extending, modifying, or removing berdctl commands, verbs, nouns, schemas, help text, or any of the berdctl surface.
- ▌ Experimental Features · blockUse when adding, reviewing, configuring, graduating, or removing Berd experiments.
- ▌ Proto Regen · blockUse when editing any `.proto` file under `proto/` or `server/sdk/v1/pb/`, or modifying root/server `buf.yaml`, `buf.gen.yaml`, or `buf.lock`. Protobuf changes require regenerating Go, TypeScript, and SDK code via `just gen`; without it, server handlers, client API hooks, SDK consumers, and plugins compile against stale shapes.
- ▌ Asicrs Build · blockUse when editing files under `plugin/asicrs/`, `sdk/rust/`, or `server/sdk/v1/pb/` (which the asicrs build also consumes). The ASIC-rs plugin is a Rust binary built via Docker and cached against an `.asicrs-platform` marker; source changes that bypass `just _asicrs-build` or `just rebuild-plugin asicrs` will leave the loaded plugin stale.
- ▌ Go Work Sync · blockUse when editing any `go.mod` or `go.sum` under `server/`, `plugin/`, or `tests/`, or when modifying root `go.work` / `go.work.sum`. Module dependency changes require running `go work sync` from the repo root so workspace lock data stays consistent.
- ▌ Hermit Tooling · blockUse when a shell command in this repo fails with "command not found" for `just`, `buf`, `golangci-lint`, `goimports`, `lefthook`, `ruff`, or any other developer tool. The repo pins its toolchain via Hermit (`.hermit/`); the tools exist on disk but only resolve after the Hermit environment is activated.
- ▌ Plan Conventions · blockUse when editing or creating files under `docs/plans/` (TDDs, PRDs, lightweight plans). Enforces frontmatter (`title`, `date`, `status`, `type`) and the `draft → proposed → accepted → implementing → completed | cancelled` status lifecycle.
- ▌ Client Boundaries · blockUse when editing files under `client/src/shared/`, `client/src/protoOS/`, or `client/src/protoFleet/`. Enforces app-import boundaries (`shared/` cannot import apps; `protoOS` and `protoFleet` cannot import each other) and the no-new-`console.log` rule (`console.error` and the existing build-version logger are fine).
- ▌ Fake Rig Fixtures · blockUse when editing `server/fake-antminer/` or `server/fake-proto-rig/`. These are test doubles consumed by `tests/plugin-contract/`, the E2E suites, and the local `just dev` stack — behavior changes here ripple silently into all three surfaces.
- ▌ Docker Compose Dev · blockUse when editing `server/docker-compose.yaml` or `server/docker-compose.base.yaml`, or when troubleshooting a `just dev` startup. Proto Fleet requires Docker host networking on macOS/Windows; service definitions split between `base` (shared) and the runtime override file.
- ▌ Python Gen Tarball · blockUse whenever the user changes any source under `packages/proto-python-gen/` (Python source, `setup.sh`, `requirements.txt`, `bin/`) or edits `scripts/pip-config.sh` (which gets bundled). The Python proto generator ships as a versioned tarball that Hermit consumes; if source changes but the tarball isn't rebuilt and committed, downstream consumers silently use the stale generator.
- ▌ Buf Version Pinning · blockUse when editing `buf.yaml`, `buf.lock`, or any `buf.gen.yaml` (root, server, or SDK). Generator plugin versions in `buf.gen.yaml` are tightly coupled to the generated code consumers (Connect-RPC client, sqlc, SDK shapes); a version bump can produce a large unrelated diff and break downstream code that relies on specific output shapes.
- ▌ DB Generation Hygiene · blockUse when editing `server/sqlc/queries/**/*.sql`, `server/sqlc.yaml`, or creating a new `server/migrations/*.sql` file. sqlc query and schema source changes require running `just gen` so `server/generated/sqlc/` stays in sync. Edits to *existing* migration files are owned by the `migration-immutability` skill instead.
- ▌ Lefthook Bypass Guard · blockUse when about to run `git commit --no-verify`, `git commit -n`, `git push --no-verify`, or any command that bypasses the `lefthook` hooks configured in `lefthook.yml`. Pre-commit hooks (formatting, lint, ruff, buf-lint) and pre-push hooks (typecheck, golangci-lint) catch real problems; bypassing them shifts the failure to CI and produces noisier PRs.
- ▌ Plugin Contract Tests · blockUse when editing miner-protocol code under `plugin/proto/`, `plugin/antminer/`, or `plugin/virtual/`, or when changing test fixtures consumed by `tests/plugin-contract/`. The contract suite is the canonical check that a plugin still meets the miner driver contract; it is Docker-heavy and easy to skip, but plugin behavior regressions only surface here.
- ▌ Migration Immutability · blockUse when modifying an existing `server/migrations/*.sql` file already on `main`. Deployed migrations are immutable — `golang-migrate` skips already-applied versions, so editing one in place silently desyncs schemas across environments. Corrective changes must go in a new migration.
- ▌ Proto Fleet Playwright E2e · blockUse when adding, fixing, or reviewing Playwright E2E coverage in the block/proto-fleet monorepo, especially after a feature is already implemented. Covers scenario design, spec and page-object changes, local env-aware verification, simulator-safe cleanup, and follow-up on E2E PR comments or CI failures.
- ▌ Rp Why · block bundleLoad when reflecting on AI collaboration quality or tracking growth over time. Analyzes session history to surface how deeply you think with AI tools and whether your orchestration sophistication matches your cognitive depth. Provides actionable nudges to push toward more strategic work.
- ▌
- ▌
- ▌
- ▌
- ▌