agentsclimarketplace

Ship & operate

32,344 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

  • Launch strategy

    kennyolofsson23-netizen/claude-code-config/skills/launch-strategy Skill

    no license0★ repo

    When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas.

    The same file is in 3 other repositories

  • React best practices

    kennyolofsson23-netizen/claude-code-config/skills/react-best-practices Skill

    no license0★ repo

    React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

    The same file is in 2 other repositories

  • Appstore prepare for release

    jimmynotjames/simple-recurring-budgets/.claude/skills/appstore-prepare-for-release Skill

    no license0★ repo

    Collaboratively drive an App Store release using docs/app-store-release-checklist.md — creates (or resumes) a per-release snapshot in releases/app-store-release-checklist--vX.Y.Z.md, walks the checklist with the user across sessions, invokes the sibling appstore/translation skills for the heavy steps, and closes out by filling the RELEASES.md entry after the ~1-week post-release monitoring window. Use when starting an App Store release, resuming one mid-flight (e.g. "the app got approved", "let's check on the release"), or closing one out. Invoked via /appstore:prepare-for-release.

  • Appstore push release build

    jimmynotjames/simple-recurring-budgets/.claude/skills/appstore-push-release-build Skill

    no license0★ repo

    Build and upload the App Store release-candidate build — confirms the release checklist has been worked through, prompts for the new App Store version number, bumps MARKETING_VERSION on a release branch, then runs `fastlane ios beta` so the candidate lands in TestFlight (auto-bumps build number from ASC, archives, uploads, auto-commits the pbxproj bump), then pushes, opens a chore PR, waits for CI, and squash-merges. The same binary is then manually tested via TestFlight and attached to the App Store version in ASC — one build serves both. Does NOT submit for review — that stays a manual App Store Connect step. Use when the release checklist reaches the release-candidate build step, or when asked to push a release build. Invoked via /appstore:push-release-build.

  • Appstore push testflight build

    jimmynotjames/simple-recurring-budgets/.claude/skills/appstore-push-testflight-build Skill

    no license0★ repo

    Build and ship a TestFlight build end-to-end — creates a release branch, runs `fastlane ios beta` (auto-bumps build number from ASC, archives, uploads, auto-commits the pbxproj bump), then pushes, opens a chore PR, waits for CI, and squash-merges. Use when cutting a new TestFlight build. Invoked via /appstore:push-testflight-build.

  • Cloudkit deploy schema

    jimmynotjames/simple-recurring-budgets/.claude/skills/cloudkit-deploy-schema Skill

    no license0★ repo

    Deploy this app's CloudKit record schema from the Development environment to Production, safely — includes preflight checks and mandatory human-confirmation gates before anything destructive or production-affecting. Use when promoting a new or changed CloudKit schema to Production (including the first-ever/greenfield deploy for a new container), or when asked to update/sync the Production CloudKit schema.

  • Appstore prepare for release

    jimmynotjames/simple-recurring-budgets/.cursor/skills/appstore-prepare-for-release Skill

    no license0★ repo

    Collaboratively drive an App Store release using docs/app-store-release-checklist.md — creates (or resumes) a per-release snapshot in releases/app-store-release-checklist--vX.Y.Z.md, walks the checklist with the user across sessions, invokes the sibling appstore/translation skills for the heavy steps, and closes out by filling the RELEASES.md entry after the ~1-week post-release monitoring window. Use when starting an App Store release, resuming one mid-flight (e.g. "the app got approved", "let's check on the release"), or closing one out. Invoked via /appstore:prepare-for-release.

  • Appstore push release build

    jimmynotjames/simple-recurring-budgets/.cursor/skills/appstore-push-release-build Skill

    no license0★ repo

    Build and upload the App Store release-candidate build — confirms the release checklist has been worked through, prompts for the new App Store version number, bumps MARKETING_VERSION on a release branch, then runs `fastlane ios beta` so the candidate lands in TestFlight (auto-bumps build number from ASC, archives, uploads, auto-commits the pbxproj bump), then pushes, opens a chore PR, waits for CI, and squash-merges. The same binary is then manually tested via TestFlight and attached to the App Store version in ASC — one build serves both. Does NOT submit for review — that stays a manual App Store Connect step. Use when the release checklist reaches the release-candidate build step, or when asked to push a release build. Invoked via /appstore:push-release-build.

  • Cloudkit deploy schema

    jimmynotjames/simple-recurring-budgets/.cursor/skills/cloudkit-deploy-schema Skill

    no license0★ repo

    Deploy this app's CloudKit record schema from the Development environment to Production, safely — includes preflight checks and mandatory human-confirmation gates before anything destructive or production-affecting. Use when promoting a new or changed CloudKit schema to Production (including the first-ever/greenfield deploy for a new container), or when asked to update/sync the Production CloudKit schema.

  • Biz case workflow

    hsnuhow/how-skills/plugins/taiwan-biz-research/skills/biz-case-workflow Skill

    no license0★ repo

    Run a full Taiwan business case end-to-end as a hypothesis-driven multi-agent workflow — frame the question as 2-4 mutually exclusive strategic options, reverse-engineer what-would-have-to-be-true conditions per option, surface the key debates with bull and bear both argued, run skeptic-designed tests in a lazy-man loop that kills options early and expands the search when evidence runs dry, build a driver-tree market model with analog-market parameterization, profile competitors symmetrically, then choose the option with the fewest unresolved barriers and ship a monitoring plan. Use when someone asks for a Taiwan market-entry, sizing, competitor, investment or timing case, an evidence-backed strategic recommendation, or "研究一下台灣的 X 市場" — anything where the answer must be a defensible choice among options. Not for a single lookup; use tw-data directly for that.

  • Mcl shared platform design

    suwa-sh/multi-cloud-lifecycle-skills/.claude/skills/mcl-shared-platform-design Skill

    0★ repo

    共有プラットフォーム設計用スキル。AWS / Azure / GCP / オンプレミスを対象に、ベンダー中立の canonical model、ベンダー別マッピング、サービスカタログ、実装仕様、IaC スケルトンを生成する。共有ランタイム(Kubernetes)、オブザーバビリティ、CI/CD デリバリーパイプライン、アーティファクト管理、シークレット/証明書管理、プラットフォーム所有モデル、テナントオンボーディングをカバーする。共有プラットフォームレイヤー、内部開発者プラットフォーム、プラットフォームエンジニアリング、共有サービスカタログ、共通インフラサービスの設計やレビューに使用すること。1 クラウドのみの言及でも発動する。EKS/AKS/GKE 共有クラスタ、集中監視、共有 CI/CD、プラットフォームチームの責務に関するトピックでもトリガーする。オンプレ Kubernetes(kubeadm/Rancher/OpenShift)やハイブリッド構成の共有プラットフォームでもトリガーする。

  • Cron task manage

    Evan-Daruwalla/claude-skill-suite/cron-task-manage Skill

    0★ repo

    Windows scheduled-task auditor, READ-ONLY execution always — the only thing it ever shells out to is `schtasks /query`. audit (default) parses the CSV task list and flags the unhealthy ones: Last Result != 0 (with the code), Disabled state, and — for an ENABLED task — a Next Run Time that is N/A or already in the past. Scope defaults to non-Microsoft tasks (--all / --like <substr> to widen or narrow). plan mode PRINTS the exact `schtasks /create` line for you to run yourself; the tool NEVER runs /create, /delete, or /change. Use when the user says "audit my scheduled tasks", "did the scheduled task run", "why did the rebalance task fail", "check the cron/scheduled job", "is that task disabled", "what's the schtasks command to create X", "cron-task-manage". --fixture parses a saved query capture offline. Deterministic, zero dependencies, no model calls.

  • Agents deploy

    dkmqflx/claude-tools/.claude/skills/agents-deploy Skill

    no license0★ repo

    Use when deploying your agent to AWS, or when a deploy has failed. Handles pre-flight validation, CDK/IAM/quota error diagnosis, version management, rollback, and canary deployments. Triggers on: "deploy my agent", "agentcore deploy", "deploy failed", "CDK error", "rollback", "canary deploy", "pin version", "redeploy", "deploy stuck". Not for production hardening — use agents-harden. Not for adding capabilities before deploy — use agents-build or agents-connect. Not for VPC configuration errors — use agents-build.

  • Agents optimize

    dkmqflx/claude-tools/.claude/skills/agents-optimize Skill

    no license0★ repo

    Use when measuring or improving agent quality and performance — set up evaluators, online monitoring, CI/CD quality gates, observability, or cost optimization. Triggers on: "evaluate my agent", "add evaluator", "measure quality", "quality gate", "run evals", "agent too slow", "why is it slow", "reduce latency", "set up observability", "CloudWatch dashboard", "how much does my agent cost", "cost optimization", "logs not showing up", "logs missing", "spans not found", "eval failing", "eval error", "dev traces", "local traces", "agentcore dev traces", "traces to CloudWatch". Not for debugging errors or crashes — use agents-debug. Slow but correct routes here; broken routes to debug.

  • Aws amplify

    dkmqflx/claude-tools/.claude/skills/aws-amplify Skill

    no license0★ repo

    Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first). Covers auth (Cognito), data (AppSync/DynamoDB), storage (S3), functions, APIs, and AI (Amplify AI Kit with Bedrock). Supports React, Next.js, Vue, Angular, React Native, Flutter, Swift, and Android. Always use this skill for Amplify Gen2 topics — even for questions you think you know — it contains validated, version-specific patterns that prevent common mistakes. TRIGGER when: user mentions Amplify Gen2; project has amplify/ directory or amplify_outputs; code imports @aws-amplify packages; user asks about defineBackend, defineAuth, defineData, defineStorage, defineFunction, or npx ampx. SKIP: Amplify Gen1 (amplify CLI v6), standalone SAM/CDK without Amplify (use aws-serverless), direct Bedrock without Amplify AI Kit (use bedrock).

  • Aws billing and cost management

    dkmqflx/claude-tools/.claude/skills/aws-billing-and-cost-management Skill

    no license0★ repo

    Analyze AWS costs, find savings, manage budgets, evaluate Savings Plans and Reserved Instances, right-size EC2/Lambda/RDS/EBS with Compute Optimizer, look up service pricing, query CUR with Athena, detect cost anomalies, scope costs to billing views, and monitor Free Tier usage. Triggers on: AWS bill, cost analysis, reduce spend, savings plan, reserved instance, right-size, budget alert, cost optimization, pricing, free tier, cost anomaly, CUR, cost audit, billing view, billing view ARN.

  • Aws cdk

    dkmqflx/claude-tools/.claude/skills/aws-cdk Skill

    no license0★ repo

    Authors, deploys, and troubleshoots AWS infrastructure using CDK with TypeScript or Python. Covers best practices, stack architecture, and construct patterns. Always use when writing CDK constructs, bootstrapping environments, running cdk deploy/synth/diff, fixing CDK or CloudFormation errors, planning stack structure, importing existing resources, resolving drift, or refactoring stacks without resource replacement.

  • Aws cloudformation

    dkmqflx/claude-tools/.claude/skills/aws-cloudformation Skill

    no license0★ repo

    Author, validate, and troubleshoot AWS CloudFormation templates. Covers template authoring with secure defaults, pre-deployment validation (cfn-lint, cfn-guard, change sets), and root-cause diagnosis of failed stacks using CloudFormation events and CloudTrail correlation.

  • Aws containers

    dkmqflx/claude-tools/.claude/skills/aws-containers Skill

    no license0★ repo

    Deploys and operates containerized workloads on ECS, Fargate, and ECR. Covers task definitions, Fargate services, ECR repository setup and lifecycle policies, ECS Exec debugging, service scaling, deployment strategies, load balancer integration, and logging configuration. Use when deploying, debugging, or optimizing containers on AWS. ALSO USE for container deployment options (ECS vs ECS Express Mode), networking modes, health check troubleshooting, OOM errors, secrets injection, blue/green deployments, ECR image management, and App Runner sunset guidance and migration. NOT for Kubernetes, EKS, or CI/CD pipelines.

  • Aws iam

    dkmqflx/claude-tools/.claude/skills/aws-iam Skill

    no license0★ repo

    Verified corrections for IAM behaviors that AI agents frequently get\ \ wrong \u2014 policy evaluation edge cases, trust policy gotchas, STS session limits,\ \ Organizations quirks, and SAML/MFA specifics. Use alongside documentation when\ \ working with IAM roles, policies, STS, or Organizations. Do NOT use for non-IAM\ \ authorization like Cognito user-pool policies or app-level RBAC.

  • Aws messaging and streaming

    dkmqflx/claude-tools/.claude/skills/aws-messaging-and-streaming Skill

    no license0★ repo

    Guides use of AWS messaging and streaming services. Covers Amazon SQS, Amazon SNS, Amazon EventBridge, Amazon MQ, Amazon Kinesis Data Streams, Amazon Data Firehose, Amazon Managed Service for Apache Flink, and Amazon Managed Streaming for Apache Kafka (MSK). Use when implementing messaging and streaming patterns.

  • Aws observability

    dkmqflx/claude-tools/.claude/skills/aws-observability Skill

    no license0★ repo

    Builds, configures, debugs, and optimizes AWS observability using CloudWatch (Logs Insights, Metrics, Alarms, Dashboards, EMF), X-Ray, CloudTrail, and ADOT. Covers Log Insights query syntax (fields, filter, stats, parse, pattern, join, subqueries), alarm configuration (metric, composite, anomaly detection, missing data treatment), dashboard design, custom metrics (PutMetricData, EMF, metric filters), X-Ray tracing (ADOT, sampling rules, annotations vs metadata), ADOT collector config, and CloudTrail auditing. Use when the user mentions CloudWatch, Log Insights, alarms, INSUFFICIENT_DATA, dashboards, custom metrics, EMF, X-Ray, traces, sampling, CloudTrail, who deleted, ADOT, OpenTelemetry, observability, monitoring, synthetics, canaries, or troubleshooting alarm behavior. Do NOT use for application logging setup, container log drivers, or security threat detection.

  • Aws sdk js v3 usage

    dkmqflx/claude-tools/.claude/skills/aws-sdk-js-v3-usage Skill

    no license0★ repo

    AWS SDK for JavaScript v3 development patterns. Use when writing JavaScript or TypeScript code that uses AWS services via @aws-sdk/* packages (aws-sdk-js-v3), or when asked about schemas, runtime validation, serialization, or code generation in the context of the JS/TS AWS SDK.

  • Aws sdk python usage

    dkmqflx/claude-tools/.claude/skills/aws-sdk-python-usage Skill

    no license0★ repo

    AWS SDK for Python (boto3/botocore) development patterns. You MUST use this skill when writing Python code that uses AWS services via boto3 or botocore. This includes creating service clients or resources, configuring sessions and credentials, handling errors with ClientError, using paginators and waiters, S3 file transfers and presigned URLs, DynamoDB table operations, and any boto3/botocore client configuration. Use this skill whenever Python code imports boto3 or botocore, or when the user asks about AWS operations in Python.

  • Aws sdk swift usage

    dkmqflx/claude-tools/.claude/skills/aws-sdk-swift-usage Skill

    no license0★ repo

    AWS SDK for Swift development patterns. Use when writing Swift code that uses AWS services via aws-sdk-swift package.

  • Aws serverless

    dkmqflx/claude-tools/.claude/skills/aws-serverless Skill

    no license0★ repo

    Builds, deploys, manages, debugs, configures, and optimizes serverless applications on AWS using Lambda, API Gateway, Step Functions, EventBridge, and SAM/CDK. Covers cold starts, CORS debugging, event source mappings, troubleshooting, concurrency, SnapStart, Powertools, function URLs, EventBridge Scheduler, Lambda layers, Durable Functions, durable execution, checkpoint-and-replay, and production readiness. Use when the user mentions Lambda, API Gateway, Step Functions, SAM templates, CDK serverless stacks, DynamoDB stream triggers, SQS event sources, cold starts, timeouts, 502/504 errors, throttling, concurrency, CORS, Powertools, Durable Functions, durable execution, checkpoint-and-replay, or any event-driven architecture on AWS, even if they don't say "serverless." Do NOT use for EC2, ECS/Fargate containers, or Amplify hosting.

  • Vercel composition patterns

    dkmqflx/claude-tools/.claude/skills/vercel-composition-patterns Skill

    no license0★ repo

    The same file is in 23 other repositories

  • Vercel react best practices

    dkmqflx/claude-tools/.claude/skills/vercel-react-best-practices Skill

    no license0★ repo

    React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

    The same file is in 7 other repositories

  • Ship

    cloverink/shipwright/skills/ship Skill

    0★ repo

    Full pipeline — audit, review+fix, docs, push PR. One command to go from "done coding" to "PR ready for review." Does NOT deploy — your CI/CD handles that after merge.

  • Git nanny

    agony1997/TouchFish-Skills/plugins/git-nanny/skills/git-nanny Skill

    0★ repo

    Git 全方位專家:涵蓋 Commit 訊息生成、Pull Request 建立與審查、分支策略管理、版本發布與 Changelog。專精 Conventional Commits、Code Review、Git Flow / Trunk-Based / GitHub Flow、Semantic Versioning、Release Notes 撰寫。關鍵字: commit, pull request, PR, branch, release, changelog, git flow, trunk-based, github flow, semantic versioning, conventional commits, code review, git tag, 提交, 分支, 版本發布, 合併請求, 程式碼審查, 更新日誌, 版本號, semver, hotfix, 緊急修復, merge, 合併, 合併策略, rebase, squash, tag, 標籤

    The same file is in 2 other repositories

  • Project

    AI-Driven-School/aiki/.claude/skills/project Skill

    0★ repo

    Run the full design-to-deploy pipeline using 3 AIs (Claude + Codex + Gemini). Use when starting a new feature, running /project, or needing end-to-end development with requirements, specs, implementation, testing, review, and deployment phases.

  • Release notes

    thinkyou0714/github-flow-kit/release-notes Skill

    0★ repo

    Generate human-readable release notes from git history and merged PRs. Creates two versions: user-facing (what's new in plain language) and developer-facing (conventional changelog format). Publishes as a GitHub Release draft with auto-suggested semver bump. Use when you're preparing a release, want to document what changed since the last tag, or need to write CHANGELOG entries. Triggers on: "リリースノート", "changelog", "release notes", "何が変わった", "バージョンアップ", "release-notes". DO NOT USE FOR: creating a new git tag, deploying to production.

  • Db telemetry primary docker logs secondary

    Ed3Design/ed3design-skill-bundles/async-forensik/skills/db-telemetry-primary-docker-logs-secondary Skill

    0★ repo

    Use when investigating missing or unexplained behavior in a containerized stack where a high-volume job (MQTT ingester, 5m-fetcher, scraper) runs in the same container as diagnostic jobs, and Docker logs show nothing for the time period in question. Symptom: `docker logs --since 72h` returns only recent lines; older diagnostic entries are gone despite the container running continuously. Root cause: Docker's default JSON log driver rotates files at ~10MB — high-volume sibling output pushes out older diagnostic lines within hours. Fix: query DB-side telemetry (tick_log, job_log, metrics tables) as primary source; Docker logs are only reliable for the last 30–60 minutes. Trigger on phrases like "docker logs shows nothing", "no logs from yesterday", "log rotation", "scheduler history gone", "where are Friday's logs". Do NOT load for fresh containers without DB telemetry infrastructure, single-process containers where log rotation isn't an issue, or log-streaming setups (Loki, CloudWatch, Datadog).

  • Ephemeral container file detection

    Ed3Design/ed3design-skill-bundles/async-forensik/skills/ephemeral-container-file-detection Skill

    0★ repo

    Use when designing or auditing Docker-based deployments BEFORE writing implementation plans that rely on files persisting across container rebuilds. Trigger on phrases like "volume mount for X", "why are the files gone", "container rebuild deleted the models", "model_path points to a file that's not there", "phantom registry in DB", "inference fails with FileNotFoundError", "before Claude build — are the prerequisites in place", "pre-flight deployment audit", "writing-plans for a Docker feature with persistent data". Detection-Pattern in 4 steps: docker inspect Mounts → ls container dir → stat birth-time → grep dump/save calls in code → if code writes but the mount list does NOT include the path → ephemeral, pre-flight STOP for the feature phase. Do NOT load for non-Docker deployments (systemd services, Kubernetes StatefulSets — different model), for read-only containers without write paths, for single-file apps without a storage layer. The maxim "read logs/code/DB first" applied to deployment prerequisites.

  • Ga skill edit tdd workflow

    Ed3Design/ed3design-skill-bundles/code-quality/skills/ga-skill-edit-tdd-workflow Skill

    0★ repo

    Use when editing or expanding an already-GA-promoted skill (suffix-less name, banner says PROMOTED) to add a new capability/class/feature. Different from `skill-tdd-promotion-workflow` which covers DRAFT→GA. This skill covers GA→GA+Capability — the failure mode is silent-rename-or-expand without RED-test for the new capability (Iron-Law violation). Trigger on phrases like "extend skill with X", "add a new class to an existing skill", "extend asyncpg-skill with JSONB", "rename GA skill + extend capability", "skill rename with content expansion", "Cycle-2 capability for promoted skill". Do NOT load for new skill from scratch (`superpowers:writing-skills`), for DRAFT→GA promotion (`skill-tdd-promotion-workflow`), for minor edit without new capability (just edit), or when the target skill doesn't exist.

  • Pre deploy code drift detection

    Ed3Design/ed3design-skill-bundles/code-quality/skills/pre-deploy-code-drift-detection Skill

    0★ repo

    Use when about to deploy a service that has multiple parallel push-sources (Mac + work-laptop + server-direct-edit + remote Claude session), to detect 3-way Git-drift between local, origin/main, and server-checkout BEFORE rsync/checkout/build destroys parallel work. Trigger on phrases like "deploy to server", "rsync to server", "server has working-tree changes", "why does origin have commits I don't have", "Mac + server-direct-edit drift", "code drift between machines". Do NOT load for first-time-setup-deploy (no parallel sources yet exist), for single-developer-single-machine workflows, for server-only-via-CI deploys (CI is the sole push-source), or for in-container-hot-reload-iteration (no rsync involved). This skill encodes a hard-won lesson: 4h lost because 15 server-commits were made before discovering that origin/main had parallel local commits (3-source drift between local, origin, and server). A 2-minute pre-flight would have prevented it.

  • Compound gate over single metric

    Ed3Design/ed3design-skill-bundles/planning-disciplines/skills/compound-gate-over-single-metric Skill

    0★ repo

    Use when designing or reviewing a Go/No-Go-Gate, Backtest-Acceptance-Threshold, ML-Model-Promotion-Criterion, A/B-Test-Verdict, or any binary decision-rule that triggers a downstream action (deploy, promote, ship, reject) based on a single metric — especially WR/Accuracy/Recall/F1/CTR. Single-metric gates have a documented failure mode: false-positive accepts where the system clears the gate while a hidden dimension regresses catastrophically. Compound-Gate (≥2 metrics with AND-conjunction) closes this hole. Trigger phrases like "WR-Gate-Verdict", "Backtest-Go-No-Go", "Accuracy-Threshold", "Model-Promotion-Criterion", "A/B-Verdict-Rule", "single-metric acceptance". Do NOT load for domains where single-metric meaningfulness is established (medical-sensitivity for binary screening, latency-SLO), theoretical discussions without downstream consequence, or metrics that already trade off two dimensions (F1).

  • Skill tdd promotion workflow

    Ed3Design/ed3design-skill-bundles/skill-system-meta/skills/skill-tdd-promotion-workflow Skill

    0★ repo

    Use when promoting an existing DRAFT/STUB skill (suffix `-DRAFT` or `-STUB` in `name:` field, OR description starts with "STUB —") to GA (auto-discoverable). Different from `superpowers:writing-skills` which covers CREATE-from-scratch — this skill covers the LIFECYCLE-STAGE from "skeleton-exists" to "production-ready". Requires Agent/Task-tool for parallel RED+GREEN subagent-Dispatch (Step 3) — if the caller does NOT have Agent-tool (e.g. running as a general-purpose-subagent themselves), STOP and report-up; do NOT silently fall back to name-rename-only. Trigger on phrases like "promote this DRAFT skill", "TDD for the remaining STUBs", "make it auto-discoverable", "skill promotion cycle", "release skill from -DRAFT", "TDD promotion cycle for N skills". Do NOT load for creating a new skill from scratch (use `superpowers:writing-skills`), for editing GA-skills (just edit), when no DRAFT/STUB-suffix exists (skill is already GA), or when target skill file does not exist (no work to do).

  • Workflow engine

    tarangdeep-goel-by/claude-harness/claude/skills/workflow-engine Skill

    0★ repo

    Use at the start of every conversation and before every task, implementation, debugging session, or completion claim. This skill governs which other skills must be invoked. You MUST check this skill before doing any work.

  • Container k8s validator

    ccronca/dotfiles/claude/skills/container-k8s-validator Skill

    0★ repo

    Validates Containerfile COPY commands and Kubernetes manifest paths for consistency. Automatically runs when working with Containerfiles or K8s manifests to ensure source paths exist and destinations match between files.

  • Grafana

    chenwei791129/agent-skills/skills/grafana Skill

    0★ repo

    Use when operating a Grafana instance from the terminal — listing/searching dashboards, querying datasources, inspecting alert rules, running PromQL/LogQL/TraceQL over metrics/logs/traces, or pulling/pushing dashboards as code (GitOps). Triggers on Grafana, gcx, PromQL, LogQL, dashboard, alerts/告警, 查 Grafana, dashboard 管理, 監控查詢. Use this instead of a Grafana MCP server or raw curl/grafana-backup/grizzly. Self-hosted focused.

  • Release skills

    mi4646/my-skills/skills/release-skills Skill

    no license0★ repo

    Universal release workflow. Auto-detects version files and changelogs. Supports Node.js, Python, Rust, Claude Plugin, GitHub Releases, annotated tags, historical release backfill, and generic projects. Use when user says "release", "发布", "new version", "bump version", "push", "推送", "release notes", "GitHub Release", or "回填 Release".

    The same file is in 2 other repositories

  • Chengyu listen all sides see clearly

    evnchn-agentic/chengyu-skills/chengyu-listen-all-sides-see-clearly Skill

    0★ repo

    Use BEFORE declaring victory / shipping / committing — get adversarial multi-angle review from at least one of three source classes (subagent, internet, other LLMs via API). Inter-links with chengyu-create-something-from-nothing — high-hallucination LLM sources behave like uncontrolled 無中生有, so apply the verify-don't-trust-verbatim discipline. Source selection via BullshitBench (canonical hallucination-rate index); high vs low hallucination both useful for different needs; escalate to the user when unclear. One of the strongest pre-ship disciplines in this catalog.

  • Devops safe ship

    YoniChechik/claude-code-config/skills/devops-safe-ship Skill

    no license0★ repo

    DevOps playbook for risky multi-step rollouts, migrations, and cutovers — incremental single-purpose PRs, inert-but-present fallbacks for one-line rollback, self-validation in prod (Chrome walkthroughs, /healthz probes, expected-vs-observed GO/NO-GO tables, negative controls), human-gated irreversible steps, CI-guard discipline, and durable milestone memory. Invoke for any high-blast-radius change e.g. auth/issuer cutovers, signing-key revokes.

  • Feature workflow

    YoniChechik/claude-code-config/skills/feature-workflow Skill

    no license0★ repo

    End-to-end feature development pipeline: plan → implement → build tests → post checks → PR → summary. Invoked by /new-feature and /continue-feature. this skill should not be invoked directly but rether by the other skills.

  • Raw workflow creator

    mpuig/raw/skills/raw-workflow-creator Skill

    no license0★ repo

    Create and run RAW workflows. Use this skill when the user asks to create a workflow, automate a task, build a data pipeline, generate reports, or asks "How do I build X with RAW?".

  • Review

    jmfontaine/jmf-claude-plugins/plugins/project-qa/skills/review Skill

    0★ repo

    Review project files for consistency, completeness, and correctness. Use when asked to review, audit, check, or validate project configuration files (justfile, Makefile, CI workflows, pre-commit config, pyproject.toml, Dockerfile, docker-compose, etc.) or documentation files (README, CLAUDE.md, CONTRIBUTING, etc.). Supports both single-file review and cross-file consistency checks.

    The same file is in 2 other repositories

  • Logging observability

    andresnator/agents-orchestrator/skills/logging-observability Skill

    0★ repo

    Trigger: logging, observability, metrics, traces. Evaluate operationally useful logging for safe refactors.

  • Skill doc sync

    Moliboy5000/.claude/plugins/cache/nyldn-plugins/octo/9.30.0/skills/skill-doc-sync Skill

    no license0★ repo

    Post-ship doc sync across project markdown. Use when: "sync docs", "update docs", "document changes", "release notes".

  • Skill rollback

    Moliboy5000/.claude/plugins/cache/nyldn-plugins/octo/9.30.0/skills/skill-rollback Skill

    no license0★ repo

    Roll back to a previous checkpoint via git — use when a change went wrong and you need to revert. Use when: AUTOMATICALLY ACTIVATE when user mentions:. "rollback" or "revert" or "undo". "go back to" or "restore checkpoint"

  • Release

    Moliboy5000/.claude/plugins/cache/omc/oh-my-claudecode/4.8.2/skills/release Skill

    no license0★ repo

    Automated release workflow for oh-my-claudecode

  • Document release

    Moliboy5000/.claude/skills/document-release Skill

    no license0★ repo

    Claude dotfile containing skills, agents etc I use.

  • Land and deploy

    Moliboy5000/.claude/skills/land-and-deploy Skill

    no license0★ repo

    Claude dotfile containing skills, agents etc I use.

  • Opencode workflow

    Moliboy5000/.claude/skills/opencode-workflow Skill

    no license0★ repo

    Full OpenCode delegation workflow — routing rules, agent-to-role mapping, model routing, invocation patterns, and examples for delegating tasks to OpenCode (GitHub Copilot). Use when delegating heavy work to OpenCode or making one-shot queries via opencode-ask.

  • Setup deploy

    Moliboy5000/.claude/skills/setup-deploy Skill

    no license0★ repo

    Claude dotfile containing skills, agents etc I use.

  • Ship

    Moliboy5000/.claude/skills/ship Skill

    no license0★ repo

    Claude dotfile containing skills, agents etc I use.

  • Tag release ansible

    ForeverAProgrammer/claude-devflow/skills/tag-release-ansible Skill

    0★ repo

    Bump the version in an Ansible Galaxy collection or role, tag the release, and push.

  • Tag release npm

    ForeverAProgrammer/claude-devflow/skills/tag-release-npm Skill

    0★ repo

    Bump the npm package version, tag the release, and push.

  • Tag release

    ForeverAProgrammer/claude-devflow/skills/tag-release Skill

    0★ repo

    Suggest and apply the next semver tag based on commits since the last tag.

  • Plan

    crustacean-dev/knowledge-skills/skills/plan Skill

    0★ repo

    Create technical architecture and planning documents. Two modes — project-level (produces .knowledge/architecture.md + .knowledge/conventions.md with directory structure, package dependencies, build pipeline, testing strategy, coding conventions, commit format, CI/CD) and feature-level (produces .knowledge/features/<feature>/plan.md + api/*.d.ts TypeScript contracts with exact data models, integration maps, and architectural decisions). Every decision includes a rejected alternative with rationale. Use this skill whenever the user wants to plan architecture, define conventions, structure a project, design how a feature should be built technically, figure out package layout or module boundaries, establish coding standards, or determine build/test/CI workflows. Trigger on "plan", "plan <feature>", "architecture", "conventions", "how should we build this", "design the system", "structure the project", "what should the technical approach be", "figure out the data model", or any request to make technical decisions before implementation begins. Requires .knowledge/constitution.md to exist — if missing, redirects to /constitution. Does NOT produce specs (user-facing behavior), tasks (implementation breakdown), or code (implementation). Does NOT read or summarize existing documents — it creates new planning artifacts through a structured interview.