Showing 20191–20220 of 54263 skills
Quick install of the Google Workspace CLI (gws) on an additional machine using existing OAuth credentials. Requires client_secret.json from a previous gws-setup. Use whenever the user wants to install gws on a new computer, reinstall after a fresh OS, configure a second workstation, or says 'install gws', 'gws on new machine', 'set up gws again'.
jezweb/claude-skills
Set up the Google Workspace CLI (gws) from scratch. Guides through GCP project creation, OAuth credentials, authentication, and installing 90+ agent skills for Claude Code. Use whenever the user wants to set up gws for the first time, configure Google Workspace API access, install the Google Workspace CLI, or troubleshoot gws auth issues.
jezweb/claude-skills
Plan, draft, audit, and publish content for Instagram. Use when the user wants to write a caption with a first-125-char hook, plan a slide-by-slide carousel, reverse-engineer the hook from a viral Reel or carousel, size hashtags the 2026 way, remove AI tells from a caption, or plan a week of Reels and carousels. Instagram requires media on every post, so the skills write the caption and the user supplies the image or video; posts publish via the Publora API draft, upload, schedule flow.
sergebulaev/instagram-skills
Plan, draft, audit, and publish content for Instagram. Use when the user wants to write a caption with a first-125-char hook, plan a slide-by-slide carousel, reverse-engineer the hook from a viral Reel or carousel, size hashtags the 2026 way, remove AI tells from a caption, or plan a week of Reels and carousels. Instagram requires media on every post, so the skills write the caption and the user supplies the image or video; posts publish via the Publora API draft, upload, schedule flow.
sergebulaev/instagram-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent, managed harness agent, Copilot harness, voice agent, create/update/invoke/evaluate agent, add tool to agent, agent insights, batch/continuous eval, continuous monitoring, agent CI/CD, optimize/improve prompt, optimize agent instructions, Agent Optimizer, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure-prepare).
microsoft/skills
Use when authoring or modifying browser-rendered visual output: HTML, CSS, React SSR, artifact templates, markdown renderers, design tokens, themes, or composed pages. Do not invoke for an ordinary /view render—the checked-in renderer already owns its theme contract. The load-bearing rule is that theme-sensitive colors must be emitted as `var(--token)`, never resolved inline hex; the colors themselves come from the design system registry.
egregore-labs/egregore
Operate real pi, agy, Claude, and Codex sessions in Herdr to diagnose tool behavior from transcripts, ask a CLI directly when its own behavior is unclear, then implement, retest, and redeploy a verified fix.
Pixel-CLI/pixel
Run one of eight standard prompts in two Codex panes side by side in Herdr, one with Pixel's prompt-submit brief and one without, then compare tool calls, answers and wall time. One command runs, one aborts.
Pixel-CLI/pixel
Replay Pixel's new-user setup in Docker without an LLM — install through a release archive, install.sh, the Homebrew tap, or sources from main, a PR head or a pinned commit; then personal Claude/Codex/pi settings kept, idempotent reinstall, first pixel audit, doctor and --fix, project install, disabled classify and uninstall; with --agents, Claude Code, Codex and pi sessions against a scripted fake model show whether each receives the Pixel prompt, runs pixel and routes grep. Use for Linux setup smoke checks, not macOS behavior or real model inference.
Pixel-CLI/pixel
Mine this project's local agent transcripts for the tool sequences a brief probe could replace: /extract-probes, 'mine transcripts for probes', 'which tool sequences could the brief replace'. Ranks the most common pre-answer call sequences by question kind and maps each to an existing probe or a candidate.
Pixel-CLI/pixel
Find deepening opportunities in pixel's crates (shallow modules to merge behind a smaller interface, leaking seams, logic only testable past its interface), scouted with pixel's own churn, size, caller and area data, presented as a local HTML report of before/after cards with their real cost (diff size, mutants, ARCHITECTURE.md sections, PR stack), then grilled through the candidate the user picks until it becomes a task on project 3. Adapted from Matt Pocock's improve-codebase-architecture skill. Manual only: "/improve-codebase-architecture [area]", "revue d'archi", "où approfondir les modules".
Pixel-CLI/pixel
Mine the last 24 h (or a given window) of pixel usage — every repo's `.pixel/actions.jsonl` plus the agent transcripts indexed by `pixel recall` (claude, codex, pi…) — for frictions pixel actually caused, verify each one against the current binary and code, and propose ranked, evidence-backed improvements (bug fix, error message, flag, agent prompt, rule, doc); for the pixel repo itself, also measure each pull request from first edit to validated CI and where agents sat idle (`lead_time.py`). Suggests only; implements nothing without the user's pick. Use when the user says "/pixel-retro", "retro pixel", "qu'est-ce qui a coincé avec pixel", "améliorations pixel depuis les transcripts", "pixel friction", "où l'agent attend", "bottleneck", "lead time", or asks what to improve in pixel or its development workflow from recent sessions.
Pixel-CLI/pixel
Write or revise a pixel pull request body: fill .github/pull_request_template.md (Closes #N, Summary with a call-tree, file-tree or pseudocode sketch built from pixel's own graph, before/after Evidence with commands, Merge Danger as door and blast radius, Docs touched). Use when opening a PR, rewriting its description, or answering a reviewer who asks what a PR does or risks. Adapted from Matt Pocock's MIT pr skill and HumanLayer's MIT show-me skill (UPSTREAM pins both).
Pixel-CLI/pixel
Redesign one or two sections of the pixel-cli.dev home (website/layouts/index.html) with the loop the hero went through for task
Pixel-CLI/pixel
Install Pixel from a repository, start Claude Code, Codex, pi, agy and Devin in one Herdr grid in random order, send each the same neutral prompt, and judge per CLI from evidence only whether the prompt-submit brief and a Pixel metrics line reached it. Use for /ultima-arena, 'ultima arena', 'test brief and metrics across all CLIs', or after a change to a hook, relay or install.
Pixel-CLI/pixel
Use Pixel for bounded evidence when a code question asks for an exact symbol definition or export, or the files affected by a rename. Do not use for unrelated questions.
Pixel-CLI/pixel
Use Pixel for bounded evidence when a code question asks for an exact symbol definition or export, or the files affected by a rename. Do not use for unrelated questions.
Pixel-CLI/pixel
Generate RFC and IMPL documents from a user-provided feature/fix description. Use when the user says something like "I want to add a feature with codex", "Implement this", "Write an RFC for...", or provides a short idea that needs to be formalized into the ai-driven/rfc + ai-driven/impl pipeline.
SepineTam/mcp-for-stata
Prepare or publish a Stata-MCP version from master, including lint, version metadata, and GitHub Release notes. Use for release preparation, patch releases, or publishing an approved version.
SepineTam/mcp-for-stata
Use when working on accessibility, a11y, WCAG, ARIA, screen readers, keyboard nav, focus order, contrast, alt text, captions, reduced motion, or target sizes; not language/culture/device (see inclusive-design).
evanca/flutter-ai-rules
Use when working on inclusion, i18n/localization, global name/address forms, low-end devices, slow/metered networks, affordability, or first-time/low-confidence users; not WCAG/screen readers (see accessibility).
evanca/flutter-ai-rules
Use when testing RevenueCat purchases/subscriptions, setting up sandbox testing, debugging a purchase/restore/trial, verifying entitlements or events, checking an app is ready for a RevenueCat experiment, or writing an IAP QA plan.
evanca/flutter-ai-rules
The evidence-gated calibration loop for any tunable surface - drive weights, need sigmoids, gate rho, thresholds, dispatch narrowing, eval bars, UQ calibrators, rig-posture cells. Verdict-first authority, per-group evidence census, pre-registered bars and falsifiers, hardened queue cycles that die loud in pre-flight, separate calibration and production cells, box-state provenance on every number, per-group classification with honest NO VERDICT. Use BEFORE planning or running any calibration or tuning sweep, when a calibration run keeps dying pre-run, when pinning perf bars from a calibration run, when adjudicating Calibrated vs Sparse vs Fallback, or when asked how a calibration went. Sibling to build-hygiene (pre-registered A/B bars) and grammar-not-answers (contamination gates).
katopz/katgpt-rs
Universal Do/Don't doctrine for opening and maintaining upstream pull requests as an agent — the trust rules distilled from real campaign rounds (slop tells, review-comment handling, CI triage, reply voice, force-push hygiene, rate ceilings). Use when opening a PR to any external repository, responding to a maintainer review, deciding whether a change is PR-worthy, writing or rewriting a PR/comment body, or triaging red CI on our PR; also when asked "how do we PR into X". Complements the campaign-specific skills (riir-refine's outbound-pr = the gated healer campaign lane; this one is the repo-agnostic etiquette + failure taxonomy).
katopz/katgpt-rs
Security audit workflow for this Rust workspace — trust-boundary-first review with a coverage ledger, three-verdict findings (confirmed / needs_validation / rejected), and fix-verification gates. Use for security questions, focused reviews of wire, FFI, or secrets surfaces, or a full six-phase audit when the user asks for one.
katopz/katgpt-rs
Use when working with the kubeadm CLI — bootstrapping Kubernetes clusters, init/join/reset/upgrade workflows, the phase system, certificate management, bootstrap tokens, kubeconfig generation, and the v1beta4 configuration API. Triggers on: "kubeadm", "kubeadm init", "kubeadm join", "kubeadm reset", "kubeadm upgrade", "kubeadm config", "kubeadm token", "kubeadm certs", "kubeadm kubeconfig", "kubeadm version", "kubeadm alpha", "bootstrap token", "InitConfiguration", "ClusterConfiguration", "JoinConfiguration", "ResetConfiguration", "NodeRegistrationOptions", "control-plane-endpoint", "discovery-token", "certificate-key", "feature-gates", "skip-phases", "static pod manifest", "TLS bootstrap", "kubeadm-config".
carapace-sh/carapace-bin
Writes high-converting landing pages, hero headlines, cold outreach emails, social hooks, video intros, and SERP titles using the Hook, Spike, and Payoff copywriting system. Use when rewriting flat marketing copy that explains instead of sells, or when the user mentions "blitz copy", "dopamine copywriting", or conversion hooks.
Illyism/seo-skills
Builds a buyer-psychology research brief covering customer pains, switching triggers, objections, inner monologue, and verbatim phrasing before writing a word of copy. Use when researching an ICP before landing page or ad copy, or when the user mentions "understand customers", "empathy engine", or "customer pain points".
Illyism/seo-skills
Map how customers discover, evaluate, and choose a product across Google, AI chatbots (ChatGPT, Claude, Perplexity), and social platforms, using the 5-stage awareness journey. Use when the user asks about search intent, AI SEO prompts, discoverability, buyer journeys, awareness stages, or what content to create for a brand, website, or keyword list.
Illyism/seo-skills
Runs a focused 30-day SEO sprint that concentrates search-intent alignment, internal link equity, first-hand proof, and targeted backlinks onto a single money page to push it into the Top 3. Use when a high-value page is stuck on Page 2, the user mentions "blitz seo" or a 30-day SEO sprint, or SEO effort is spread too thin across dozens of URLs.
Illyism/seo-skills