Loading...
Loading...
Found 99 Skills
Databricks documentation reference. Use as a lookup resource alongside other skills and MCP tools for comprehensive guidance.
Noyo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Noyo data.
Use when the task involves an external library or package and current API docs are needed before writing code.
Authoritative reference for Pi (@earendil-works/pi-coding-agent): install, configure, run, and extend. Use when the user asks about Pi CLI/flags/commands, providers/models/auth, settings/compaction/sessions, security/trust, extensions, skills, prompt templates, themes, packages, custom providers, TUI components, the SDK, RPC mode, or JSON streaming. Also use for Pi's design philosophy and opinionated choices (why minimal, 4 tools, YOLO, no MCP/plan mode/to-dos/sub-agents), the creator Mario Zechner's coding-agent blog post, Pi's internal monorepo architecture (the Chord plugin/service runtime (@earendil-works/chord), the agent harness, facets/services, delta tracking), and the repository's build, development, and contribution rules.
Shared scripts, fragments, and bundled files used by all RootSpec skills — not meant to be invoked directly
GeoDB Cities integration. Manage Cities, Countries, Continents. Use when the user wants to interact with GeoDB Cities data.
Delegate a coding task to the GitHub Copilot CLI (`copilot`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Copilot - phrasings like "have Copilot implement X", "delegate this to copilot", "run it through Copilot CLI", or "use copilot to implement/fix/refactor" - or wants to run a queue of coding tasks through Copilot while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.
Get an independent, read-only review from OpenAI Codex (via the codex CLI, on whatever model and reasoning effort the user names, else Codex's configured default) of uncommitted changes, a branch, specific files or a plan, then verify every finding against the real code yourself, accept/reject/defer each one, implement only the accepted fixes, and report a verdict table. Use whenever the user asks for a Codex review, a second opinion, a cross-check or sanity check by another model or GPT, says 'ask Codex', 'have Codex look at this', 'get a second pair of eyes', or wants an independent reviewer before merging, shipping or executing a change or plan, even if they don't mention this skill by name.
Navigate unfamiliar code using GitNexus knowledge graph
Solana hackathon resource advisor for Colosseum builders. Use when a builder asks which sponsor tools, SDKs, RPC providers, wallets, identity, payments, privacy, governance, NFT, game, mobile, DeFi, or developer resources to use for a hackathon project.
Bring a blocked React Router community pull request across the finish line. Use when the user invokes `/finish-line` or `$finish-line`, provides a PR number or URL, and asks Codex to resolve merge blockers such as a missing change file, missing documentation, missing tests, or stale contributor follow-up. Handles evaluating the blocker and pushing small maintainer fixes onto a contributor PR branch when authorized.
Turn hand-made first-50 traction into self-reinforcing acquisition loops, so the next 5,000 users come from usage, not founder hours. Use when growth stalls the moment the user stops pushing, every signup traces back to a DM or one launch spike, or they're reaching for "more channels" when the real gap is that using the product creates no new users.