Loading...
Loading...
Found 11,797 Skills
Build with the Terra API Planned Workouts product (pre-release) – define a structured workout once and Terra API pushes it to users' devices. Use when pushing planned or structured workouts to Garmin, COROS, Wahoo, Suunto, TrainingPeaks, Huawei, Zepp, Hevy, or Apple watches, building training plans or workout templates, working with intervals, warmups, targets (HR, power, pace, cadence, RPE, zones), FTP or threshold-based personalization, athlete parameters, swimming or strength templates, or handling provider coercion warnings when a device cannot represent a feature.
UiPath bug reports and improvement suggestions via `uip feedback send`. Use for 'report issue', 'send feedback', 'file a bug', or the /uipath-feedback command. For investigating an error rather than reporting one→uipath-troubleshoot.
UiPath Coded Functions — deterministic Python units built via `uip function` (new/init/run/pack/publish); the `functions` map in `uipath.json`, `entry-points.json`, Pydantic Input/Output. Rule-based logic, data transforms, ERP/Integration Service connector calls — no LLM reasoning or agent loop. For LLM/agentic projects (LangGraph, LlamaIndex, OpenAI Agents, `agent.json`)→uipath-agents.
Write a commit message body by deriving it from the code, not by summarizing the diff. Weighs the change, then either answers seven questions against the implementation — what forces it, which call paths reach it, how it failed, what breaks on update, what the tests pin — or produces a two-to-three-line body for mechanical and generated changes. Not for full commit creation.
Release an npm, pnpm, or bun package: version bump, validation, git tagging, and publishing, with safety checks and explicit user approval before anything is pushed.
Set up and maintain a repository's agent instruction layer — one real root instruction file, an AGENTS.md symlink so every agent reads the same document, a comment-convention block, and a drift check that catches documented commands, paths, structures, and counts that no longer match the repo.
Audit package.json scripts for naming, composition, lifecycle hooks, consistency, and performance.
Manage working documents in an Obsidian vault using a two-tier system — Inbox for quick dumps, Dev/Claude for persistent docs. Creates, finds, promotes, updates, and completes working documents with proper naming, headers, and lifecycle.
Resolve git merge and rebase conflicts semi-automatically. Classifies conflicts by type (DU/UD/UU/AA/DD), auto-resolves trivial ones, and applies context-aware resolution for the rest.
Fetch and analyze Linear issue with all related context. Use when starting work on a Linear ticket, analyzing issues, or gathering context about a Linear issue.
One-time setup that maps the codebase and gathers user-provided product context to write a root PROJECT.md overview of what the project is, who it serves, how it is structured, and how it runs. Use when the user invokes $setup-project-md, says "setup project md", "create PROJECT.md", or asks for a complete project overview document at the repo root.
Run a complete repository-native, spec-anchored development loop inspired by DeepSeek Harness. Use for feature development, bug fixes, simplification, architecture, process, or testing work that changes behavior, contracts, structure, test strategy, durable formats, or decision rationale; when asked to write, review, continue, implement, reject, supersede, archive, or verify a spec/Agent Note/RFC/ADR; or when code, tests, current-state docs, and decision rationale must converge in one change. Also use for read-only spec-to-code drift checks. Do not create a spec for a purely mechanical local edit that changes none of those things.