Showing 8641–8670 of 10205 skills
Trace BIRD routing-daemon behavior through the actual C source tree. Use for implementation questions, suspected upstream bugs, parser/keyword origins, filter instructions, protocol state machines, route attributes, birdc commands, stack traces, or BIRD 2 versus BIRD 3 source comparisons. Prefer a local checkout or exact upstream tag/commit and cite concrete files, functions, and revisions. Route config linting to bird-agent and active incidents to bird-troubleshooting.
bird-chinese-community/BIRD.skills
Build or review GitHub Actions workflows for BIRD 2/3 projects using bird-chinese-community/setup-birdcc and @birdcc/cli. Use for pull-request lint/format/parse checks, BIRD2/BIRD3 matrices, BIRD_BIN, changed config files, pnpm/Turbo caching, submodule configs, action pinning, or .github/workflows changes. Route local config work to bird-agent and local editor/CLI installation to birdcc-installer.
bird-chinese-community/BIRD.skills
Dynamic multi-agent workflows — plan first, then orchestrate parallel agents with adversarial verification via the local odw daemon. Use when the user asks for a "workflow", says "ultracode", or hands you a task spanning many files/items that benefits from parallel agents.
Suraj1235/open-dynamic-workflows
Dynamic multi-agent workflows — plan first, then orchestrate parallel agents with adversarial verification via the local odw daemon. Use when the user asks for a "workflow", says "ultracode", or hands you a task spanning many files/items that benefits from parallel agents.
Suraj1235/open-dynamic-workflows
Dynamic multi-agent workflows — plan first, then orchestrate parallel agents with adversarial verification via the local odw daemon. Use when the user asks for a "workflow", says "ultracode", or hands you a task spanning many files/items that benefits from parallel agents.
Suraj1235/open-dynamic-workflows
How this arcade ships as an installable PWA: the service worker's cache strategy and version bump, the deliberate no-skipWaiting decision and the update prompt that completes it, what is safe to precache and what is not, and the stale-build trap that makes a fix look like it did not work. Use when touching public/sw.js, the manifest, offline behaviour, caching, or when a change you just built is not showing up in the browser.
gagandeepgill/puzzle-game
React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.
gagandeepgill/puzzle-game
Register and update yourself as an agent (ERC8004) on BNB Chain (BSC Testnet). Use this skill to give the agent an on-chain identity without needing BNB for gas (sponsored via MegaFuel Paymaster). Supports registering a new agent, getting agent info, and updating agent metadata/endpoints.
kbarbel640-del/skills
Converts Claude Code skills to Gemini CLI extensions and vice versa. Use when the user wants to make a skill cross-platform compatible, port a skill between platforms, or create a universal extension that works on both Claude Code and Gemini CLI.
kbarbel640-del/skills
AI Agent Prediction Arena - Predict Kalshi market outcomes, compete for accuracy
kbarbel640-del/skills
This skill should be used when configuring, troubleshooting, or extending a Home Assistant OS (HAOS) instance — installing add-ons/apps, editing configuration.yaml, setting up Tailscale/remote access, or troubleshooting onboarding, the Supervisor, or backups, or building automations/scripts/helpers/template switches/webhooks through HA's REST and websocket APIs. Trigger phrases include "Home Assistant add-on", "Home Assistant apps", "configuration.yaml", "HAOS", "Home Assistant Tailscale", "Supervisor", "HACS", "home assistant api", "create automation via api", "/api/config/automation/config", "input_boolean/create", "timer/create", "home assistant websocket", "template switch config flow", "webhook local_only", "ios shortcut webhook", "template value should be a string", "pause for 1 hour then revert".
jackson2w/claude-code-skills
This skill should be used when running Ollama headless on a Mac as an always-on service, when Ollama returns HTTP 403 to requests arriving through a reverse proxy or Tailscale Serve, when deciding whether to enable macOS auto-login for a headless box, when choosing a model size for an 8GB Apple Silicon machine, or when a Caddy reverse proxy returns HTTP 200 with an empty body. Trigger phrases include "ollama headless mac", "ollama 403 proxy", "ollama Host header", "OLLAMA_ORIGINS not working", "brew services doesn't start until login", "LaunchDaemon vs LaunchAgent", "mac mini always on service", "ollama tailscale serve", "8GB unified memory model size", "caddy 200 empty body", "caddy site matcher Host".
jackson2w/claude-code-skills
This skill should be used whenever a working session pauses rather than completes — when Will says "good pause point", "let's pause here", "I'll pick this up later", "that's enough for today", "wrapping up", "done for now", or hands work back while something is still mid-flight. It defines the pause-handoff email sent to Will covering unverified claims, owed work, phrases to resume each thread, and steps only he can run. Also applies when he asks to "email me the flags", "send me what's outstanding", "what do I need to do", or "how do I pick this up later".
jackson2w/claude-code-skills
Make any PrestaShop module expose its business logic to AI agents through the official PrestaShop MCP Server (ps_mcp_server). Covers the discovery contract, a Composer-free PSR-4 autoloader, and ready-to-use templates for Tools, Resources, Resource Templates and Prompts.
ecomyseo/prestashop_skills
This skill should be used when a developer wants to open a pull request for a completed trace branch — for example "create a PR", "open a pull request", "submit this for review", "make a PR for trace
xiduzo/wtf
This skill should be used when a developer or lead wants a project status overview — what is blocked, stale, unverified, or waiting on a next step — for example "project health check", "what's blocking the release", "standup summary", or "what's left in this epic". Scans all open WTF issues — Traces plus legacy Tasks — and produces a triage-ready health report with actionable next steps.
xiduzo/wtf
This skill should be used when something is broken in production and needs an immediate fix that bypasses the normal Epic→Feature→Trace planning flow — for example "production is down", "hotfix needed", "critical bug in prod", "emergency fix for
xiduzo/wtf
This skill should be used when a developer is ready to implement, resume, or continue a GitHub Trace issue — for example "implement trace
xiduzo/wtf
This skill should be used when a developer wants to autonomously execute all Traces under a fully-specified Epic or Feature — for example "go", "start building", "implement everything", "run the loop", "execute the feature", "build it all", "kick it off". Requires that the Epic/Feature/Trace tree is fully written before starting. Chains implement → verify → PR → re-aim for every Trace — spine-first within each Feature, parallel across Features — with targeted human-in-the-loop gates for contradictions, ambiguities, and every change to a Trace Plan's scenario set.
xiduzo/wtf
This skill should be used when a developer or tech lead wants to review a pull request for correctness, spec adherence, and code quality — for example "review PR
xiduzo/wtf
This skill should be used when a team wants to close out a completed Epic or sprint, capture what was planned vs. what shipped, learn from deviations, and formally mark the Epic done — for example "run a retro on this epic", "close out the epic", "what deviated from the plan", "retrospective for epic
xiduzo/wtf
This skill should be used when a user wants to set up WTF in a repository or check that the environment is ready for it — for example "set up wtf", "is wtf ready", "install wtf templates", or "a new dev joined, set them up". Verifies the GitHub CLI and its auth, installs the required gh extensions and the issue and PR templates, configures issue classification, planning, feature scope, and delivery mode, and registers the hooks. Run once per repo when onboarding, or when a contributor joins the project.
xiduzo/wtf
This skill should be used when a developer or tech lead needs to investigate a technical unknown before committing to an approach — for example "run a spike on X", "I need to research this before writing the epic", "we don't know how to approach this yet", "investigate if we can use X for Y", "time-box this exploration", "what's the right architecture for this?", or "should we use A or B?". Produces a findings document and a concrete recommendation that feeds directly into write-epic or write-trace.
xiduzo/wtf
This skill should be used when a user wants to create, draft, or plan a GitHub Epic issue — for example "write an epic", "I want to define a new initiative", "scope out this strategic project", "turn this idea into an epic", "plan work that spans multiple features", or "start from a bounded context". Also use when the user asks to define domain outcomes, capture a large initiative before breaking it into features, or describe work in terms of business goals rather than implementation details.
xiduzo/wtf
This skill should be used when a user wants to create a GitHub Feature issue, break down an Epic into user-facing capabilities, write user stories in domain language, or capture what a domain actor can do — for example "create a feature", "write a feature for this epic", "add a feature to an epic", "break this epic into features", "write user stories for this feature", or "describe what this actor can do". Use this skill to write a single Feature. Use `wtf.epic-to-features` to generate the full set of Features for an Epic at once. Supports two planning modes — `guided` (step-by-step questions) and `flow` (derive, one consolidated review) — passed as an argument or read from `.wtf/config.json`. Not applicable to Traces, Epics, or bug reports.
xiduzo/wtf
This skill should be used when a user wants to create a single Trace issue under a Feature — for example "create a trace", "write a trace for this feature", "add a trace to feature
xiduzo/wtf
Turn the current project, a GitHub PR URL, a URL-backed app, or a supplied evidence path into a short polished project showcase video (25 s default, 10-90 s accepted) with a poster image, a written plan, a composition brief, and ready-to-paste share copy. Use when the user says "showoff this project", "make a demo video", "create a showcase reel", "showcase what I built", "turn this PR into a video", "make a shareable clip of my work", "make a highlight reel", "create a product demo", or "record what this app does". Inspects the source, plans a grounded narrative, composes a HyperFrames video, bakes the strongest settled frame as the poster, and writes share copy. ShowOff never automatically publishes or uploads the finished artifacts. It may contact supplied PR/app hosts, Claude Code, HyperFrames update sources, and explicitly approved Media OS providers.
All-The-Vibes/ShowOff
One-time setup wizard that generates a personalized skill-creator. Use when the user has just installed this boilerplate and wants to configure it, says 'set up the skill creator', 'configure the boilerplate', 'let's set this up', 'I want to start making skills', or asks how to get started with this repo. Runs once, asks eleven questions about naming conventions, versioning, layout and scope, plus one for what to call the result, then writes a ready-to-use skill-creating skill. Do NOT use this to create an individual skill -- that is what the generated tool does afterwards.
colomet/skill-boilerplate
Guide for writing ast-grep rules to perform structural code search and analysis. This skill should be used when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search, or when a simple grep/glob search is insufficient for structural code pattern matching.
archibate/dotfiles-opencode
Skill to define requirements effciently as a product manager.
archibate/dotfiles-opencode