troykelly

Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning

Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type and priority, creates well-formed GitHub issues with proper project board integration.

MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.

Use for LARGE work requiring feature-level grouping. Creates epic tracking issues, manages related issues under a common label, tracks epic progress, and coordinates with milestones.

Use when the user wants to design Codex agent equivalents (specialized workers/profiles/prompt files), define triggering conditions, or build reusable agent prompts and validation tools.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Use when the user wants to create Codex workflow hooks (pre/post run gates, tool-use validators, stop checks) or needs guidance on hook scripts and hooks.json configuration.

Analyze and resolve Sentry comments on GitHub Pull Requests. Use this when asked to review or fix issues identified by Sentry in PR comments. Can review specific PRs by number or automatically find recent PRs with Sentry feedback.

Use after creating PR - monitor CI pipeline, resolve failures, address review feedback, and merge when all gates pass

Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type and priority, creates well-formed GitHub issues with proper project board integration.

MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.

Use to spawn isolated worker processes for autonomous issue work. Uses Task tool with run_in_background for parallel execution and TaskOutput for monitoring. Pre-extracts context to minimize worker token usage.

Defines behavior protocol for spawned worker agents. Injected into worker prompts. Covers startup, progress reporting, exit conditions, and handover preparation.

Use when user requests autonomous operation across multiple issues. Orchestrates parallel workers using Task tool, monitors with TaskOutput, handles SLEEP/WAKE cycles, and works until scope is complete without user intervention.

Use for any development work - the master 13-step coding process that orchestrates all other skills, ensuring GitHub issue tracking, proper branching, TDD, code review, and CI verification

Use when starting any work session - establishes autonomous operation mode, overriding token limits and time pressure to work until goal is achieved

Project management, memory storage, and communications backend for OpenClaw agents

Onboard a new external API, configure credentials, and verify endpoints

Build a comprehensive view of a contact with relationships, links, and memories

Generate a summary report for a completed dev session

Audit namespace content by searching across projects, memories, and items

Create meeting notes with attendees, action items, and linked references

Set up a new terminal connection with credentials and verification

Comprehensive weekly review of projects, tasks, communications, and sessions

Autonomous single-orchestrator build loop. ONE Claude session (the orchestrator) fans out agent teams via ultracode Workflows to drive the whole repo toward done — identifying next work, then shipping correctness/robustness/tests/docs/API/auth/observability/UX, gap-reviewing, backlogging the gaps, and shipping those too. Selects the right model per job. Runs for days. Trigger: `/loop /orchestrate`. The ONLY exit is a genuinely dry repo (no work, no UX to improve) — never a "natural break point".

Outbound call to ask about the price, stock, or availability of a product or service on the operator's behalf, and report back what you learn. Load this when placing a call whose objective is a price or availability enquiry.

Door or gate intercom: handle a delivery (parcel, food, courier) and open the entry only for a genuine, expected delivery. Load this when answering a door intercom and the visitor says they are delivering something.

Outbound call to book a reservation on the operator's behalf (a restaurant table, an appointment, a booking). Load this when you are placing a call whose objective is to make a booking.

Answer an inbound call as a polite receptionist screening an unknown caller: greet, find out who is calling and why, answer general questions, and decide what happens next. Load this when handling an inbound call from an unknown or untrusted caller.

Take a message from a caller: capture who is calling, the best callback number, and the message itself, read it back to confirm, and record it for the operator. Load this when a caller wants to leave a message.

Store and recall persistent project memory via the local qdrant memory MCP (qdrant-store / qdrant-find). Recall at the start of non-trivial tasks; store non-obvious decisions, operator feedback, and hard-won lessons when you learn them.

Record an architecture decision as an ADR in docs/adr/. Use whenever a non-trivial design or tooling decision is made (technology choice, data model, protocol, security posture) — before or alongside the implementing commit.

Control Home Assistant Music Assistant - browse library, search, play, manage preferences and moods.

Control Home Assistant Music Assistant (speakers, search/library, play) with optional local "music memory".

Query Transport for NSW (TfNSW) public transport data for Sydney and NSW, Australia. Use when: (1) checking next train, bus, ferry, or light rail departures, (2) planning trips between stations or locations, (3) finding nearby stops/stations, (4) checking public transport schedules in Sydney/NSW, (5) commute planning. Supports stop lookup, departure boards, trip planning, and Home Assistant person entity location resolution.