agentsclimarketplace

Ship & operate

32,362 rows, by stacks then stars

1,245 of these skill files have been read, by 1,077 distinct authors, and what they tell an agent counted. What Ship & operate authors agree on, and what they forbid

  • Screenshot automation

    akhilkannur/marketing-agent-blueprints/skills/screenshot-automation Skill

    no license4★ repo

    Automatically captures, crops, and beautifies screenshots from URLs for your portfolio or docs.

  • Tech hygiene audit

    EdytaKucharska/keel/v2-backlog/tech-hygiene-audit Skill

    4★ repo

    Audits a product's technical hygiene — backups, secrets, observability, deployment, basic security, testing on critical paths, and the operability of any AI-generated code. Produces a ranked list of "needed yesterday" items (non-negotiable) vs. "you don't need this yet" items (defer with a trigger). Use this skill PROACTIVELY when the user asks "is my system production-ready", "audit my project", "what should I clean up before [investors / customers / scaling]"; mentions shipping with AI tools (Cursor, Claude Code, v0, Lovable, Bolt) and wants to know if the code is solid; mentions a near-miss (leaked secret, data scare, surprise bill); or shares a repo, deployment config, or system description. Especially important for solo vibe coders who shipped working code but don't know what's load-bearing or fragile. Produces a structured audit with the artifact mapped first, items ranked by urgency, AI-generated code evaluated against three explicit tests, and a concrete two-week professionalisation plan.

  • Software development

    toolbox-playground/super-claudio/skills/software-development Skill

    4★ repo

    Software development skill. Use when the user wants to build, code, automate, or deploy anything technical. Covers backend APIs, databases, workflow automation, scripts, free public APIs, and hosting/deployment. Trigger on backend: "build an API", "REST API", "database schema", "Supabase", "Firebase", "PostgreSQL", "MongoDB", "FastAPI", "Express", "Fastify", "GraphQL", "Node.js server", "Python API", "Prisma", "ORM", "authentication backend", "serverless functions". Trigger on automation: "automate this", "connect these apps", "n8n", "Make.com", "Zapier", "when X happens do Y", "no-code automation", "schedule a script", "webhook", "automate posting", "IFTTT", "auto-post to Instagram", "batch processing", "automate email". Trigger on free APIs: "free API for X", "public API", "build a weather app", "NASA API", "real-time data", "open data", "free data source", "API without credit card", "government API". Trigger on deployment: "deploy my app", "Docker", "Railway", "GitHub Actions", "CI/CD", "hosting", "go live", "containerize", "VPS setup". Trigger on git/GitHub: "create a PR", "open a pull request", "GitHub CLI", "gh pr", "gh issue", "connect Claude to GitHub", "GitHub MCP", "commit message", "git workflow", "manage issues", "review a PR", "GitHub Actions workflow", "release on GitHub". Do NOT trigger for: frontend/UI design (use design skill), media generation (use media-content-creation).

  • Supreme npm node

    davccavalcante/supreme-coding-guidelines-skill.ah/skills/supreme-npm-node Skill

    no license4★ repo

    Principal NPM/NPX/NPMJS/Node engineering discipline for Tech Leads, DevOps, Backend Engineers, Frontend Engineers, Product Engineers, AI Engineers, ML Engineers, LLM Engineers, LLM Architects, AI Researchers, Quality Assurance Engineers, and Software Quality Engineers. Enforces a latest-version-always policy (never pin to definitive versions; always `ncu -u` before install), TypeScript strict mode with every check enabled (strict + noUncheckedIndexedAccess + exactOptionalPropertyTypes + useUnknownInCatchVariables + noImplicitOverride), `satisfies` over `as`, `unknown` over `any`, discriminated unions over optional flags, branded types for opaque identifiers. Covers Node ecosystem (current LTS or latest stable), package.json discipline (files allowlist over .npmignore, exports map with import/require/types conditional, engines node range, type:module default), publishing workflow (`npm pack --dry-run` preview, OIDC provenance attestation in GitHub Actions, semantic versioning via changesets/release-please, dist-tag next/beta/canary for previews), supply-chain reliability (npm audit gate, lockfile committed, no untrusted postinstall, attw type-correctness check), monorepo support (pnpm workspaces preferred), and continuous upgrade cadence (`ncu -u` weekly + Renovate/Dependabot + codemods on breaking upgrades). Requires ah-parser. Output mode follows the user preference set at parser activation; user package.json, lockfile, scripts, and command output are always preserved verbatim.

  • Feature launch playbook

    rampstackco/claude-skills-pm/skills/feature-launch-playbook Skill

    4★ repo

    The operational playbook for launching a feature well. Positioning, internal alignment, customer comms, sales enablement, support readiness, rollout strategy, monitoring with pre-defined rollback triggers, post-launch measurement against spec hypotheses, and the discipline that distinguishes shipping from releasing from actually launching. Triggers on launch plan, feature launch, launch checklist, ship vs release, rollout strategy, gradual rollout, sales enablement, support readiness, launch announcement, post-launch measurement, launch failure, declared victory too early. Also triggers when planning a launch (any size, any segment), auditing an existing launch process, fixing the we shipped it but the metric did not move problem, or building a launch checklist for the team.

    The same file is in 1 other repository

  • Changelog voice

    Dragoon0x/product-skills/skills/communication/changelog-voice Skill

    no license4★ repo

    Ship updates people actually want to read. Structures release notes, changelog entries, and product updates with what-changed, why-it-matters, and what-to-do-next. Use when writing changelogs or release announcements.

  • Story commentary workflow

    JWCodeWrote/Agent_Skills_Plugin/story-commentary-workflow Skill

    no license4★ repo

    A specialized Agent Skill for organizing game story footage, planning story commentary videos, splitting chapters, transcribing subtitles, drafting narration, and matching narration to visuals. Use when the user mentions story commentary, game plot recaps, story condensation, chapter breakdowns, narration scripts, voiceover-to-visual mapping, or no-timeline editing workflows.

  • Inference known good config

    cfregly/gpu-perf-tune/plugins/profile-and-optimize/skills/inference-known-good-config Skill

    4★ repo

    Capture + enforce per-model KNOWN-GOOD serving configs: the REQUIRED serve flags (boot-blockers / crash-at-high-c / deploy-correctness workarounds) plus the champion + the bug each flag avoids, in one queryable registry (perf-tune-report/configs/known-good-configs.yaml) so a hard-won workaround (e.g. Qwen3-Next's gdn_prefill_backend=triton on vLLM 0.22) is NEVER re-discovered the hard way. These are NOT well-known upstream defaults -- several are field-discovered workarounds where the upstream `auto` path is actively broken on the target hardware. `record` after a champion is found, `check` (fail-closed) before any deploy/ship. Keep the registry private -- never post an entry publicly. Triggers on "known-good config", "required flags for <model>", "did we capture the flag combo", "register the config", "check the deploy config", "config drift", "what flags does <model> need", or any combination of "known-good / required / champion config" with "record / check / register / capture / drift / flags / serve".

  • K8s troubleshooting

    cfregly/gpu-perf-tune/plugins/profile-and-optimize/skills/k8s-troubleshooting Skill

    4★ repo

    Expert Kubernetes troubleshooting assistant for diagnosing and resolving issues across the full stack - pods, control plane, nodes, networking, storage, and underlay infrastructure - in GPU cloud environments. Triggers on any report of a broken, degraded, or mysterious Kubernetes issue: pod crashes, OOMKills, scheduling failures, network problems, CRD errors, node NotReady, high latency, PVC issues, GPU/InfiniBand problems, workload hangs, or any cluster incident. Also triggers when the user pastes error messages, kubectl output, alert names, or incident-channel links and wants help understanding what's wrong. This skill works iteratively - it does NOT dump a wall of diagnostics all at once. It pauses after each step and asks the user how to proceed.

  • Prometheus anchored query

    cfregly/gpu-perf-tune/plugins/profile-and-optimize/skills/prometheus-anchored-query Skill

    4★ repo

    Agent Skills and an MCP server for GPU performance profiling, benchmarking, optimization, and reporting, with an inference focus.

  • Ship

    magarcia/skills/skills/ship Skill

    4★ repo

    Take a finished local change through verification, UI checks, pull-request publication, CI and review follow-up, and the user-authorized merge outcome. Use when implementation is complete and the user says "ship it" or "get this merged," or as the final stage of $build. Do not use to implement new feature scope.

  • Incident rollback

    megandmartin/agent-skills-repo/skills/agent-mastery/incident-rollback Skill

    4★ repo

    The response protocol for when an agent did something wrong in the real world — stop the agent, assess blast radius, contain (revoke keys, undo changes), communicate to affected parties, write the post-mortem, and add a prevention rule to the responsible skill's Pitfalls. Use when the user says "the agent sent/deleted/bought something it shouldn't have", "kill the agent", "roll this back", "we have an incident", or any agent action caused unintended real-world effects. Don't use for outputs that are merely wrong but caused no harm — that's prompt-debugger.

  • Changelog release notes

    megandmartin/agent-skills-repo/skills/builder-dev/changelog-release-notes Skill

    4★ repo

    Turn raw commit history into two artifacts — an internal changelog (complete, technical) and user-facing "What's New" notes (benefit-first, jargon-free). Use when the user says "write release notes", "what's new for this version", "changelog since last release", "announce the update", or is tagging/shipping a version. Don't use for writing project setup docs — use docs-readme-writer.

  • Git ship flow

    megandmartin/agent-skills-repo/skills/builder-dev/git-ship-flow Skill

    4★ repo

    Safe git workflow for non-developers — init, branch, commit, push, open a PR, and undo mistakes without losing work. Use when the user says "commit this", "push my changes", "make a branch", "open a PR", "I messed up git", "undo my last commit", or is shipping code and doesn't know git well. Don't use for reviewing someone else's PR diff — use github-pr-review.

  • Vercel deploy check

    megandmartin/agent-skills-repo/skills/builder-dev/vercel-deploy-check Skill

    4★ repo

    Pre-deploy gate and post-deploy verification for Vercel — env vars set, build passes locally, no secrets shipped to the client, then live status, key routes, and console errors checked after. Use when the user says "deploy this", "is it safe to ship", "push to production", "the deploy broke", or "check the live site". Don't use for scanning the repo for leaked keys in git history — use env-secrets-hygiene.

  • Ops agent persona

    megandmartin/agent-skills-repo/skills/paperclip-workforce/ops-agent-persona Skill

    4★ repo

    Persona and protocol for the operations agent in a Paperclip org — scheduling, report compilation, file hygiene, and recurring-job monitoring; the org's reliability layer that surfaces every anomaly and never silently fixes one. Use when acting as the ops agent, when a ticket asks to "schedule", "compile the report", "clean up the files", "check the crons", or "why didn't the job run". Don't use for synthesizing the weekly retro narrative — that's weekly-retro.

  • Stale alerts analyzer

    conallob/o11y-analysis-tools/skills/stale-alerts-analyzer Skill

    4★ repo

    Query a live Prometheus's historical ALERTS series to find alert rules that haven't fired in a long time — "dead code analysis" for alerting rules, surfacing candidates for deletion or threshold review. Use interactively during alert-quality/on-call hygiene reviews, not as a CI gate. Requires a live Prometheus with sufficient ALERTS retention.

    The same file is in 1 other repository

  • Ship issue

    jerseycheese/agent-skills/skills/ship-issue Skill

    4★ repo

    End-to-end conductor that drives a single GitHub issue all the way to a merged PR. Chains the issue-workflow skills — sync the base branch, analyze the issue, implement a minimal fix with a test, open a PR, drive CI to green, confirm the merge, run post-merge cleanup, and wrap up. Use to take one issue from a cold start to merged in a single command. Trigger on "ship issue #X", "ship #123", "take #N to merge", "do issue #X end to end", "full issue loop for #N", "run the whole issue #X".

  • Test workflow

    jerseycheese/agent-skills/skills/test-workflow Skill

    4★ repo

    Automatically run after editing source files to select and run the appropriate test suite. Triggers on: any src/ file edit before a commit, or when the user says "run tests", "check tests", or "make sure tests pass". Selects unit, E2E, visual regression, or CSS lint based on what changed. Protects running dev servers. Do NOT wait for user to ask after a code change — run proactively before committing. Not for documentation-only or config-only edits, or when the user says to skip tests.

  • Eval and safety harness

    impactbrussels/AINativeOS/skills/eval-and-safety-harness Skill

    4★ repo

    Use when a founder says "is this safe to ship", "it hallucinated to a customer", "it made up a citation", "we need clinical/food-safety/financial guardrails", "how do I evaluate this", "the demo worked but I'm scared to launch", "what if it's wrong about a dose", or is in health, food, or finance and an answer could walk out into a person. Triggers on eval set, golden cases, adversarial cases, regression, critic/judge, LLM-as-judge, deterministic fallback, human-on-the-loop, red-team, release gate. Produces a binary safety rubric, a critic/judge pairing, named fallbacks, and the human boundary. Skill turns a stacked-deck demo into a gated harness; without it, the wrong answer reaches a user unchecked.

  • Gateway agent ops

    impactbrussels/AINativeOS/skills/gateway-agent-ops Skill

    4★ repo

    Use when one agent is trying to do every operational job and it is drifting, getting confused, or running up a bill - when the founder says "my agent does everything", "it routed a refund through the wrong logic", "it got stuck in a loop all weekend", "the prompt is 4000 words and nobody can touch it", "I got a four-figure API bill", "should I build one big assistant for ops", or wants to automate the boring operational tail safely. Produces a routing map (request classes to specialist agents), a classification schema, and the loop and cost guardrails. Run after write-the-claude-md; pairs with self-healing-fallbacks.

  • Red team the agent

    impactbrussels/AINativeOS/skills/red-team-the-agent Skill

    4★ repo

    Use when an agent is about to meet real users or an auditor and you need to attack it first, the way a hostile user or a security reviewer would. Reach for this when you say "try to break it", "can someone jailbreak this", "is it injection-safe", "what if a user lies to it", "the agent has tools and I am scared", "prove it is hard to abuse", or before a launch, a pen test, or a security questionnaire. Distinct from eval-and-safety-harness, which builds the general eval substrate and guardrails: this is the offensive, adversarial attack suite and the loop that runs against them. Produces a red-team attack suite (categories plus concrete attacks), a severity x exploitability scoring rubric, and a pass/fail release gate wired before ship. Invoke after eval-and-safety-harness, before design-the-mva.

  • Github actions updater

    lynicis/actup/skills/github-actions-updater Skill

    4★ repo

    Helps users keep GitHub Actions workflow files up to date. Use when the user mentions GitHub Actions, workflow files, upgrading actions, bumping action versions, CI/CD maintenance, or deprecated actions.

  • 05 website rebuild

    mhrsdev/AI-Agent-Skills-Library/organized-skills/website-business-builds/05-website-rebuild Skill

    4★ repo

    Full website rebuild agent. Takes an existing website URL and rebuilds it from scratch into a world-class, SEO-optimized, WCAG AA accessible, visually stunning website using Astro + Tailwind CSS, deployed to Vercel via GitHub. Executes a rigorous 14-phase process: brand extraction, content scraping, SEO audit, design audit, rebuild planning, full build with design system, copy optimization, 3 QA rounds, competitive tools research, tools build, tools QA, pre-deploy checklist, and Vercel deployment. Produces 11+ documentation deliverables. Triggers on: "rebuild website", "redesign website", "rebuild site from URL", "website rebuild", "redo this website", "make this website better", "rebuild from scratch", "full site redesign", or any request to take an existing URL and create a new, professional website from it. Also triggers when the user provides a URL and asks to build/create/design a new version of that site.

  • Python release

    Paldom/python-skills/skills/python-release Skill

    4★ repo

    Cuts and automates releases of a Python package — version bumps, changelogs, git tags, PyPI trusted publishing (OIDC), and the tag-triggered publish workflow with a gated environment. Use for 'cut a release', 'publish to PyPI', 'bump the version', 'automate releases', 'set up trusted publishing'. Not for packaging metadata, build backends, or non-release CI.

  • Python supply chain

    Paldom/python-skills/skills/python-supply-chain Skill

    4★ repo

    Hardens a Python repository's supply chain — Dependabot update automation, pip-audit vulnerability scanning, secret scanning and push protection, CodeQL, OpenSSF Scorecard, SBOMs, CODEOWNERS. Use for 'set up dependabot', 'audit dependencies', 'enable secret scanning', 'harden this repo'. Not for CI quality gates, workflow hardening, or PyPI publishing.

  • Agent scheduled tasks

    adsagents/adsagent-ai-skills/skills/agent-scheduled-tasks Skill

    4★ repo

    AdsAgent tri-channel AI skills for Meta, Google Ads, and TikTok hosted MCP

  • Apidog test automation

    apidog/apidog-cli-skills/.well-known/agent-skills/apidog-test-automation Skill

    no license4★ repo

    Apidog test automation, suites, and CI: test-suite, scheduled-task, runner, apidog run, execution parameters, iteration data, report upload, and CI regression. Use apidog-test-scenario for complex test-scenario step modeling.

  • Apidog workflow api lifecycle

    apidog/apidog-cli-skills/.well-known/agent-skills/apidog-workflow-api-lifecycle Skill

    no license4★ repo

    Apidog API lifecycle workflow: from requirements to API design, schemas, environments, mocks, test cases, documentation export/publishing, and branch merge. Use when creating a group of APIs and completing tests, mocks, or docs.

  • Cloudflare block countries

    oleg-koval/agent-skills/packages/software-development/cloudflare-block-countries Skill

    4★ repo

    Block specific countries via Cloudflare WAF Custom Rules using the Cloudflare API. Use when user wants to geo-block traffic, block countries in Cloudflare, set up WAF country rules, or mentions blocking regions. Handles both creating new rulesets and updating existing ones.

  • Cloudflare block countries

    oleg-koval/agent-skills/packages/software-development/cloudflare-block-countries/adapters/claude/skills/cloudflare-block-countries Skill

    4★ repo

    Block specific countries via Cloudflare WAF Custom Rules using the Cloudflare API. Use when user wants to geo-block traffic, block countries in Cloudflare, set up WAF country rules, or mentions blocking regions. Handles both creating new rulesets and updating existing ones.

  • Cloudflare block countries

    oleg-koval/agent-skills/packages/software-development/cloudflare-block-countries/adapters/cursor/skills/cloudflare-block-countries Skill

    4★ repo

    Block specific countries via Cloudflare WAF Custom Rules using the Cloudflare API. Use when user wants to geo-block traffic, block countries in Cloudflare, set up WAF country rules, or mentions blocking regions. Handles both creating new rulesets and updating existing ones.

  • Cloudflare block countries

    oleg-koval/agent-skills/packages/software-development/cloudflare-block-countries/adapters/grok/skills/cloudflare-block-countries Skill

    4★ repo

    Block specific countries via Cloudflare WAF Custom Rules using the Cloudflare API. Use when user wants to geo-block traffic, block countries in Cloudflare, set up WAF country rules, or mentions blocking regions. Handles both creating new rulesets and updating existing ones.

  • Semantic release beta

    oleg-koval/agent-skills/packages/software-development/semantic-release-beta Skill

    4★ repo

    Set up or update a Node.js release pipeline that uses semantic-release-npm-github-publish with a stable main channel and a prerelease beta channel on a beta branch, including GitHub Actions validation and npm publishing behavior.

  • Semantic release beta

    oleg-koval/agent-skills/packages/software-development/semantic-release-beta/adapters/claude/skills/semantic-release-beta Skill

    4★ repo

    Set up or update a Node.js release pipeline that uses semantic-release-npm-github-publish with a stable main channel and a prerelease beta channel on a beta branch, including GitHub Actions validation and npm publishing behavior.

  • Semantic release beta

    oleg-koval/agent-skills/packages/software-development/semantic-release-beta/adapters/cursor/skills/semantic-release-beta Skill

    4★ repo

    Set up or update a Node.js release pipeline that uses semantic-release-npm-github-publish with a stable main channel and a prerelease beta channel on a beta branch, including GitHub Actions validation and npm publishing behavior.

  • Semantic release beta

    oleg-koval/agent-skills/packages/software-development/semantic-release-beta/adapters/grok/skills/semantic-release-beta Skill

    4★ repo

    Set up or update a Node.js release pipeline that uses semantic-release-npm-github-publish with a stable main channel and a prerelease beta channel on a beta branch, including GitHub Actions validation and npm publishing behavior.

  • Docker

    RealTapeL/SkillPilot/test_openclaw_python/skills/docker Skill

    no license4★ repo

    Manage Docker containers and images

  • Breach incident response

    vaquarkhan/compliance-agent-skills/skills/breach-incident-response Skill

    4★ repo

    Executes USA breach and security incident response—HIPAA Breach Notification Rule (45 CFR §164.400–414), HITECH 60-day notification, state breach laws, and SOC 2 CC7.4/CC7.5 incident management—for agent, MCP, and LLM-related events. Trigger when investigating suspected PHI/PII exposure, unauthorized MCP access, LLM data leakage, or preparing breach notifications. Do not use for preventive logging design (use audit-logging-integrity) or routine vulnerability scanning.

  • Soc2 ccm continuous monitoring

    vaquarkhan/compliance-agent-skills/skills/soc2-ccm-continuous-monitoring Skill

    4★ repo

    Implements Continuous Control Monitoring (CCM) for SOC 2—automated control testing, configuration drift detection, predictive risk scoring, and alerting—for agent platforms, MCP servers, and cloud infrastructure. Trigger when building always-on compliance dashboards, detecting TSC control drift between audits, or operationalizing CC4/CC7 monitoring. Do not use for one-time evidence binders (use soc2-evidence-collection) or initial TSC mapping (use soc2-trust-services-criteria).

  • Deployment safety

    05-deepak-patidar/claude-skills/deployment-safety Skill

    4★ repo

    Safe shipping to production on any platform (Render, Vercel, AWS, Docker, bare VM). Use when deploying, releasing, configuring CI/CD, writing Dockerfiles or infra config, running migrations against production, or when the user says "deploy", "release", "go live", "ship", "rollback", or "production".

  • Observability readiness

    05-deepak-patidar/claude-skills/observability-readiness Skill

    4★ repo

    Logging, metrics, tracing, alerting, and audit trails so production problems are diagnosable from the outside. Use when adding logging, setting up monitoring or alerts, instrumenting a service, preparing for launch, or when the user says "logging", "monitoring", "observability", "alerts", "metrics", "audit trail", or "how do I know if it's working in prod".

  • Release readiness

    05-deepak-patidar/claude-skills/release-readiness Skill

    4★ repo

    The final gate before any launch, major release, or "is this production-ready?" question — orchestrates all engineering-discipline skills into one go/no-go review. Use when the user says "ready to launch", "production ready", "go live checklist", "release", "ship it", "pre-launch review", or before delivering a milestone to real users/clients.

  • Hello env

    Songhonglei/better-agent-skills/skills/hello-env Skill

    4★ repo

    Zero-dependency Bash environment health check for Linux, macOS, containers, and K8s pods. Reports OS, current user, Node.js, Python3, basic tools (git/curl/jq/make/docker) with paths and versions, network (hostname, IP, inferred subnet), container/K8s detection with a configurable env-var probe, workdir and git status, optional config-file check, and PVC remount detection (device-number plus watch-dir count snapshot diff to catch silent K8s PersistentVolume reattach to a fresh disk). Three-layer config — CLI flags override env vars override defaults. Trigger when user wants to check the environment, verify a dev box is healthy, detect container or K8s context, look up local IP or subnet, see Node and Python versions, list installed basic tools, or watch for silent PVC rotation in K8s pods. Also triggers on 检查我的环境, 环境自检, hello-env, 查看系统信息, 环境有没有问题, IP 是多少, 在什么环境, PVC 换卷了吗, 基础工具检查, node 版本, 当前用户是谁.

  • Release pastiche

    retz8/pastiche/.claude/skills/release-pastiche Skill

    4★ repo

    Ship a pastiche release — version bump, plugin build, CHANGELOG entry, release commit, tag, GitHub Release, milestone close. Use when the user invokes `/release-pastiche` after a TODO group's final feat→main merge. Human-triggered only; never run from an automated routine.

  • Cloudflare to bun

    DaleSeo/bun-skills/skills/cloudflare-to-bun Skill

    4★ repo

    Migrate Cloudflare Workers to Bun with runtime compatibility analysis. Use when converting Workers to Bun, migrating from Cloudflare bindings, or moving from edge to server deployment.

    The same file is in 2 other repositories

  • Pre release

    marcfargas/skills/pre-release Skill

    4★ repo

    Pre-release review and changeset generation for npm packages using @changesets/cli. Use when: preparing a release, generating changelogs, pre-release checklist, version bump, writing release notes, reviewing README before publish. Triggers: "prepare release", "pre-release", "generate changelog", "write changesets", "release checklist".

  • Yocto ci release

    prashantdivate/awesome-yocto-ai-agent-skills/yocto-ci-release Skill

    4★ repo

    Yocto CI, reproducible build, and release engineering skill for AI coding agents. Use for kas, repo manifests, Git submodules, containerized builds, CI runners, downloads and sstate caches, hash equivalence, PR build gates, QEMU tests, hardware smoke tests, artifact publishing, SDK releases, SBOM/license manifests, release notes, and version pinning.

  • Yocto deploy flash

    prashantdivate/awesome-yocto-ai-agent-skills/yocto-deploy-flash Skill

    4★ repo

    Yocto deployment and board flashing skill for AI coding agents. Use when locating deploy artifacts, choosing WIC/SDIMG/EXT4/TAR/BMAP/UBI/UBIFS/NAND/NOR/eMMC/SD/QSPI/DFU/TFTP/NFS artifacts, flashing images with bmaptool, dd, fastboot, UUU, STM32CubeProgrammer, U-Boot, vendor tools, or verifying serial boot logs and first-boot behavior.

  • Community ops creator assets

    ShiroRyu9/community-ops-kit/skills/community-ops-creator-assets Skill

    4★ repo

    Use when identifying, nurturing, or operating community creators, contributors, superusers, ambassadors, featured members, user-generated content, showcases, tutorials, case studies, attribution, permissions, or turning submissions into reusable community/product content assets.

  • Community ops daily report

    ShiroRyu9/community-ops-kit/skills/community-ops-daily-report Skill

    4★ repo

    Use when turning daily community operations into a concise daily report, daily log, work recap, owner update, standup note, or personal community-ops record. Separates completed public actions, drafts, analysis, follow-ups, risks, data gaps, and tomorrow actions without overstating unconfirmed work.

  • Community ops expression

    ShiroRyu9/community-ops-kit/skills/community-ops-expression Skill

    4★ repo

    Use when writing, rewriting, reviewing, or polishing community-operations language, including announcements, activity posts, reminders, result posts, daily/weekly reports, public articles, skill descriptions, resume bullets, interview stories, stakeholder updates, and natural-language edits. Trigger when the user asks for writing that sounds human, concrete, less templated, less AI-like, or free of repetitive contrast patterns.

  • Community ops onboarding

    ShiroRyu9/community-ops-kit/skills/community-ops-onboarding Skill

    4★ repo

    Use when designing, auditing, or improving community newcomer journeys, onboarding questions, welcome flows, first-action prompts, start-here pages, role/access routing, activation checklists, or early retention paths across Discord, forums, Slack, product/customer communities, creator communities, or private groups.

  • Community ops paid members

    ShiroRyu9/community-ops-kit/skills/community-ops-paid-members Skill

    4★ repo

    Use when designing or reviewing paid-member, premium, VIP, membership-tier, customer, subscriber, high-value user, renewal, benefit, exclusive activity, priority support, discount, entitlement, or member-retention operations. Keeps benefits explicit, evidence-based, and approval-gated.

  • Community ops router

    ShiroRyu9/community-ops-kit/skills/community-ops-router Skill

    4★ repo

    Use when diagnosing, designing, coordinating, operationalizing, or reviewing an end-to-end community operations system; when a request spans onboarding, activities, creators, paid members, reports, automation, support risk, operator writing, SOPs, or AI/bot/operator handoffs; or when the correct specialist community-ops skill is unclear. Produces a routed workflow with user segment, friction, next action, surface, evidence, execution status, feedback loop, review rhythm, and approval boundaries.

  • Community ops support risk

    ShiroRyu9/community-ops-kit/skills/community-ops-support-risk Skill

    4★ repo

    Use when triaging community support issues, payment or access problems, moderation incidents, trust and safety concerns, permission/role changes, complaints, escalation paths, public-risk copy, evidence gaps, or operations that could affect user rights, privacy, rewards, discounts, webhooks, bots, or official claims.

  • Community ops weekly review

    ShiroRyu9/community-ops-kit/skills/community-ops-weekly-review Skill

    4★ repo

    Use when producing community weekly reviews, weekly reports, metric summaries, decision notes, retrospective plans, or next-week operating priorities. Connects activity data, onboarding, creator signals, paid/member care, support risks, content assets, and owner decisions into a practical review.

  • Cicd testing integration

    javalenciacai/QASkills/.agents/skills/cicd-testing-integration Skill

    4★ repo

    Integrate automated tests into CI/CD pipelines for continuous testing, including pipeline configuration, test automation strategies, reporting, and DevOps collaboration.

  • Pseudo agentic automation

    matt-bat/agent-command-center/skills/pseudo-agentic-automation Skill

    no license4★ repo

    Run an authorized browser or native-GUI workflow that requires runtime observation and adaptive interaction rather than a deterministic API, shell command, or existing test runner. Use for dynamic authenticated flows, browser extraction, or native GUI control; exclude ordinary Playwright test execution and deterministic file/API work.

  • Deck iteration workflow

    lossless-group/lossless-agent-skills/deck-iteration-workflow Skill

    4★ repo

    The Lossless Group's workflow for developing slides-only Astro sites for fundraise processes, aligned with the calmstorm-decks project patterns and the iterative approach from the "Develop a Slides-only Astro Site for a Fundraise Process" specification. Use when creating or modifying slide decks, managing slide variants, or implementing the structured iteration workflow for fundraise material development.