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
manastalukdar/ai-devstudio/skills/canary Skill
1★ repoMonitor a deployment for errors and regressions after shipping — polls logs, error rates, and key endpoints in a configurable loop until the deployment is confirmed healthy or a problem is detected.
manastalukdar/ai-devstudio/skills/ci-setup Skill
1★ repoConfigure CI/CD pipelines for GitHub Actions, GitLab CI, CircleCI with best practices
manastalukdar/ai-devstudio/skills/deploy-validate Skill
1★ repoPre-deployment validation with environment config, dependencies, DB migrations, and API compatibility checks
manastalukdar/ai-devstudio/skills/deployment-rollback Skill
1★ repoSafe deployment rollback with health checks and database migration reversal
manastalukdar/ai-devstudio/skills/drawio-skill Skill
1★ repoUse when the user requests diagrams, flowcharts, architecture diagrams, ER diagrams, UML / sequence / class diagrams, network topology, cloud architecture from Terraform or Kubernetes manifests, ML/DL model figures (Transformer/CNN/LSTM), mind maps, or any visualization. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that benefit from visual representation. Best suited when the diagram needs custom styling, rich shape vocabulary, swimlanes, or exportable images (PNG/SVG/PDF/JPG). Generates .drawio XML and exports locally via the native draw.io desktop CLI.
manastalukdar/ai-devstudio/skills/incident-response Skill
1★ repoStructured production incident workflow — gather symptoms, run diagnostics, correlate recent deploys, draft a timeline and incident report
manastalukdar/ai-devstudio/skills/infrastructure Skill
1★ repoInfrastructure as Code generation for Terraform, CloudFormation, and Pulumi
Observability and instrumentation
manastalukdar/ai-devstudio/skills/observability-and-instrumentation Skill
1★ repoInstrument code with structured logging, metrics, and OpenTelemetry tracing — define the on-call questions first, then work backward to the telemetry that answers them.
manastalukdar/ai-devstudio/skills/playwright-automate Skill
1★ repoBrowser automation workflows with Playwright MCP integration
manastalukdar/ai-devstudio/skills/release-automation Skill
1★ repoAutomate complete release process with versioning and publishing
manastalukdar/ai-devstudio/skills/shipping-and-launch Skill
1★ repoUnified pre-launch checklist + staged rollout strategy (0%→5%→25%→100%) + rollback triggers — consolidates deploy validation, canary monitoring, and rollback planning in one workflow.
manastalukdar/ai-devstudio/skills/sre-review Skill
1★ repoReview code and configuration for SRE concerns — SLO/SLA coverage, observability gaps, toil, alerting blind spots, and reliability anti-patterns
manastalukdar/ai-devstudio/skills/ui-harden Skill
1★ repoProduction-readiness pass for UI — audits and fixes error states, empty states, text overflow, small touch targets, and i18n gaps before shipping
hparamore/essential-claude-skills-hparamore/fable-toolkit/skills/release-readiness Skill
no license1★ repoRun a pre-ship gate that verifies a build is actually ready to deploy RIGHT NOW — build passes, core flows work, no regressions or debug residue, docs and version notes updated — and give a clear GO / NO-GO with evidence. Use whenever the user says "ready to ship?", "can I deploy this", "pre-launch check", "release checklist", "is this good to go", or asks to verify a change before deploying. Verify, don't assume — a NO-GO with reasons beats a GO that breaks prod. Not for planning which features go in a release (use project planning), writing release notes or changelogs, or executing the deploy itself — this is the go/no-go safety check that runs just before shipping.
kreek/consult/agents/.agents/skills/git-workflow Skill
1★ repoUse for branches, history edits, conflicts, rebases, recovery, force-push, and gh.
kreek/consult/agents/.agents/skills/observability Skill
1★ repoUse for observability, logs, metrics, traces, health checks, dashboards, alerts, and SLOs.
kreek/consult/agents/.agents/skills/release Skill
1★ repoUse only on request/approval for release prep, or when validation requires release artifact sync.
kreek/consult/agents/.agents/skills/workflow Skill
1★ repoUse first for every coding task to route risks, choose skills, and define proof.
kreek/consult/consult/skills/git-workflow Skill
1★ repoEngineering quality focused skills for AI coding agents that keep humans in the loop.
kreek/consult/consult/skills/observability Skill
1★ repoEngineering quality focused skills for AI coding agents that keep humans in the loop.
kreek/consult/consult/skills/release Skill
1★ repoEngineering quality focused skills for AI coding agents that keep humans in the loop.
kreek/consult/consult/skills/workflow Skill
1★ repoEngineering quality focused skills for AI coding agents that keep humans in the loop.
kreek/consult/plugin/skills/git-workflow Skill
1★ repoEngineering quality focused skills for AI coding agents that keep humans in the loop.
kreek/consult/plugin/skills/observability Skill
1★ repoEngineering quality focused skills for AI coding agents that keep humans in the loop.
kreek/consult/plugin/skills/release Skill
1★ repoUse only on request/approval for release prep, or when validation requires release artifact sync.
kreek/consult/plugin/skills/workflow Skill
1★ repoUse first for every coding task to route risks, choose skills, and define proof.
Methasit-Pun/data_engineer_claude_skills/04-architecture/cloud-data-infra Skill
no license1★ repoUmbrella skill for where data pipelines run and what they cost — AWS/GCP/Azure infrastructure (S3/GCS/ADLS layout, BigQuery/Redshift/Snowflake selection, IAM, managed-service choice, performance tuning) and cost control (bytes scanned, partition pruning, slot/credit management, storage tiering, budgets and alerts). Use this whenever the topic is cloud data infrastructure or the cloud data bill. This skill ROUTES to the focused sub-skills (cloud-infra-data, cost-optimization-data) and pulls in both when a task spans architecture and cost. Trigger on: deploying a pipeline to cloud, choosing between managed warehouses, bucket/partition layout, IAM for data access, "our BigQuery bill jumped", expensive queries, or slot/credit utilization.
Methasit-Pun/data_engineer_claude_skills/04-architecture/cloud-infra-data Skill
no license1★ repoAWS/GCP/Azure data infrastructure — S3/GCS/ADLS partitioning, BigQuery slot management, Redshift spectrum, Snowflake warehouses, IAM roles for data access, cost optimization, and managed service selection. Use this skill whenever the user is deploying a pipeline to cloud, choosing between managed data services, configuring storage for a data lake, setting up IAM/permissions for pipelines, asking about BigQuery pricing, Redshift vs. BigQuery vs. Snowflake, S3 bucket layout, or cloud-specific performance tuning. Also trigger when the user mentions cloud costs, slow BigQuery queries, Redshift concurrency scaling, storage formats in the cloud, or cross-account data access. If it touches cloud + data together, this skill should be active.
Methasit-Pun/data_engineer_claude_skills/04-architecture/data-architecture Skill
no license1★ repoObjective-first data architecture design and decision framework. Establish the target object FIRST (BI, ML, or both), elicit requirements and constraints (cloud vs. on-prem, resource/compute budget, team skills, latency and freshness SLAs, compliance), then design the layered architecture and recommend a model — evaluating cost-effectiveness per layer across Azure, AWS, and GCP. Use this skill whenever the user is planning a new data platform or a major redesign, deciding cloud vs. on-prem, choosing between clouds/warehouses at the architecture level, or asking "how should I structure this whole thing". This is a ROUTER/FRAMEWORK: it owns objective and constraint elicitation and the layer design, and delegates cloud-service specifics to cloud-infra-data and pricing detail to cost-optimization-data.
T4LEL/Claude-Arsenal/skills/ship-it Skill
1★ repoUse when deploying a project to production - first deploy or an update - or when the user says ship it, deploy, go live, push to prod, or release.
0xjitsu/jitsu-skills/skills/npm-publish Skill
1★ repoFull npm publish pipeline for scoped @0xjitsu packages. Runs pre-flight validation (package.json fields, .npmrc scope, build, tests, dry-run pack), interactive version bump (patch/minor/major), publishes to npm with public access, creates a git tag and GitHub release, then verifies the published package is installable. Triggered when the user asks to publish an npm package, release a new version, ship to npm, or cut a release.
wemwi/skill-library/global-workflow Skill
no license1★ repoMeta-Skill fuer Workflow-Steuerung und Arbeitsprotokoll. MUSS als ALLERERSTER Schritt bei JEDER eingehenden Nachricht aktiv gelesen werden — es gibt KEINEN Auto-Load, Claude muss den Skill selbst oeffnen, BEVOR recherchiert, ein anderer Skill geoeffnet oder etwas umgesetzt wird. Steuert wie Claude Aufgaben analysiert, das passende Modell waehlt, nachfragt, plant und umsetzt. Gilt projektuebergreifend fuer alle Projekte. Trigger bei JEDEM Task — neue Aufgabe, Bugfix, Feature, Refactoring UND auch reine Fragen, kurze Lookups oder wenn ein anderer Skill namentlich genannt wird. "Frage" zaehlt als Task; ein namentlich genannter Skill ersetzt das Lesen von global-workflow NICHT. Kein Task ohne diesen Skill.
t0ddharris/compound-marketing/.claude/skills/agent-browser Skill
no license1★ repoBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to 'open a website,' 'fill out a form,' 'click a button,' 'take a screenshot,' 'scrape data from a page,' 'test this web app,' 'login to a site,' 'automate browser actions,' or any task requiring programmatic web interaction.
SkillMedev/vercel-platform/skills/vercel-ai-gateway Skill
1★ repoRoute every LLM call through one unified API on Vercel - plain "provider/model" strings via the AI SDK, automatic provider routing and model fallbacks, observability and per-key cost tracking, and zero data retention. Use when you ask "how do I add an LLM to my Vercel app", "route OpenAI and Anthropic through one API", "add model failover / fallback", "track LLM cost and spend on Vercel", "set a budget per API key", "switch providers without changing code", "AI_GATEWAY_API_KEY", or "stop installing @ai-sdk/openai and @ai-sdk/anthropic separately". Do NOT use for general AI SDK app code (chat UI, tool calling, structured output) - that is the AI SDK itself; do NOT use for deploy config, env wiring, or edge/runtime choice - use vercel-deploy-pipeline, vercel-env-management, and vercel-edge-and-isr instead; do NOT use to rate-limit or block abusive AI traffic - use vercel-firewall-and-botid; and do NOT use for app-level latency/caching tuning of the route - use next-on-vercel-perf.
The same file is in 1 other repository
SkillMedev/vercel-platform/skills/vercel-deploy-pipeline Skill
1★ repoShip a Next.js app to Vercel the production way: promote a tested preview to production, instant-rollback a bad release, build once with --prebuilt, run a staged/canary rollout with Rolling Releases (GA), and wire the deploy into CI. Use when someone says "deploy to Vercel", "promote preview to production", "vercel promote", "roll back the deploy", "vercel rollback", "instant rollback", "canary release on Vercel", "rolling release", "--prebuilt build", "vercel deploy in GitHub Actions", or "set up CI for my Vercel project". Do NOT use to manage env vars or pull .env - use vercel-env-management instead; do NOT use to tune runtime/cold-start/ISR performance - use next-on-vercel-perf or vercel-edge-and-isr instead.
The same file is in 1 other repository
SkillMedev/vercel-platform/skills/vercel-edge-and-isr Skill
1★ repoChoose a rendering, runtime, and caching strategy on Vercel - Fluid Compute as the default runtime (Edge Functions are deprecated), ISR/PPR, Next.js 16 Cache Components ('use cache', cacheLife, cacheTag, updateTag, revalidateTag), and the Vercel Runtime Cache API (getCache, expireTag, invalidateByTag) with tag-based invalidation. Use when someone asks "should this page be static or server rendered on Vercel", "how do I set up ISR in Next.js", "revalidate this page on demand", or "why is my Vercel page serving stale content" - including streaming vs PPR decisions, caching an API response across regions, and migrating off unstable_cache. Do NOT use to set env vars (use vercel-env-management), wire git/preview/promote deploys (use vercel-deploy-pipeline), route LLM calls (use vercel-ai-gateway), or block bots/rate-limit (use vercel-firewall-and-botid). For pure Core-Web-Vitals/bundle tuning, hand to next-on-vercel-perf.
The same file is in 1 other repository
SkillMedev/vercel-platform/skills/vercel-env-management Skill
1★ repoManage environment variables across Vercel environments and keep local .env in sync - vercel env pull/add/rm/ls, per-environment values (development/preview/production + custom), sensitive secrets, OIDC tokens for keyless cloud access, and the NEXT_PUBLIC build-time inlining gotcha. Use when someone says "sync my .env", "vercel env pull", "set a secret on Vercel", "my env var is undefined in production", "different API key per environment", "why is my NEXT_PUBLIC var stale", or "connect to AWS/GCP without storing keys". Do NOT use when the task is the deploy/promote/rollback flow - use vercel-deploy-pipeline; for routing AI provider keys through one gateway - use vercel-ai-gateway; for runtime/region/caching config (ISR, Fluid Compute) - use vercel-edge-and-isr; for blocking bots or WAF rules - use vercel-firewall-and-botid; for bundle/runtime speed tuning - use next-on-vercel-perf.
The same file is in 1 other repository
SkillMedev/vercel-platform/skills/vercel-firewall-and-botid Skill
1★ repoHarden a Vercel app at the platform edge - the Vercel WAF (custom rules, IP blocking, managed rulesets like OWASP CRS + bot_protection + ai_bots, rate limiting), Attack Challenge Mode, system bypass rules, automatic DDoS mitigation, and BotID bot verification on sensitive routes. Use when someone says "protect my Vercel app", "add a WAF rule", "rate limit my API", "block this IP / country / user-agent", "I'm getting DDoSed", "stop bots / scrapers / AI crawlers", "turn on Attack Mode", "verify human vs bot on checkout/signup/login", or "set up BotID". Do NOT use for app-level auth/session logic - that is application code; do NOT use for env vars or secrets - use vercel-env-management; do NOT use for the deploy/promote/rollback flow - use vercel-deploy-pipeline.
The same file is in 1 other repository
afelipeg/Anthropic-Skills-for-enterprise-marketing-os/skills/weekly-control-tower Skill
1★ repoProduces weekly agency control-tower reviews covering delivery status, campaign performance, CRM activity, media pacing, blockers, SLA risk, FTE load, margin drift, and executive decisions. Use for weekly business reviews, status meetings, client control, or internal leadership updates based on MCP data access from platforms AND/OR reports uploaded (CSV, Excel, PDF). Also trigger when someone says "weekly review", "WBR", "status update", "how is the account doing?", "what happened this week?", "client health check", "control tower", or when any upstream skill flags ongoing monitoring. Even casual phrasing like "give me the weekly", "what moved?", "any blockers?", or "prep for the status call" should activate this skill.
NafisRayan/100x-Agent-Toolkit/skills/agent-browser Skill
no license1★ repoBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
NafisRayan/100x-Agent-Toolkit/skills/cloudflare Skill
no license1★ repoComprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
The same file is in 3 other repositories
NafisRayan/100x-Agent-Toolkit/skills/docker-expert Skill
no license1★ repoYou are an advanced Docker containerization expert with comprehensive, practical knowledge of container optimization, security hardening, multi-stage builds, orchestration patterns, and production deployment strategies based on current industry best practices.
The same file is in 9 other repositories
NafisRayan/100x-Agent-Toolkit/skills/n8n-code-javascript Skill
no license1★ repoWrite JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, choosing between Code node modes, or doing any custom data transformation in n8n. Always use this skill when a workflow needs a Code node — whether for data aggregation, filtering, API calls, format conversion, batch processing logic, or any custom JavaScript. Covers SplitInBatches loop patterns, cross-iteration data, pairedItem, and real-world production patterns.
The same file is in 1 other repository
NafisRayan/100x-Agent-Toolkit/skills/nextjs-developer Skill
no license1★ repoUse when building Next.js 14+ applications with App Router, server components, or server actions. Invoke to configure route handlers, implement middleware, set up API routes, add streaming SSR, write generateMetadata for SEO, scaffold loading.tsx/error.tsx boundaries, or deploy to Vercel. Triggers on: Next.js, Next.js 14, App Router, RSC, use server, Server Components, Server Actions, React Server Components, generateMetadata, loading.tsx, Next.js deployment, Vercel, Next.js performance.
The same file is in 1 other repository
NafisRayan/100x-Agent-Toolkit/skills/vercel-react-best-practices Skill
no license1★ repoReact 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 17 other repositories
NafisRayan/100x-Agent-Toolkit/skills/vercel-react-native-skills Skill
no license1★ repoA production-grade engineering toolkit for AI-assisted software development. Contains 168 specialized skill workflows (100 core + 68 GSD sub-skills), 142 expert agent personas, 24 design system specifications, 5 reference checklists, 84 slash commands, and 9 MCP server integrations.
The same file is in 18 other repositories
imtiazrayhan/agentscamp-library/skills/alerting-rules-tuner Skill
1★ repoCut alert noise and make every page mean something — rewrite alerting rules to fire on user-felt symptoms (error rate, latency SLO burn, failed requests) instead of causes (high CPU, full disk), with duration windows and severity routing so only urgent, actionable conditions reach a human. Use when on-call is fatigued by low-value pages, when real incidents get missed in the noise, or when alerts fire on causes rather than impact.
imtiazrayhan/agentscamp-library/skills/canary-release-planner Skill
1★ repoDesign a canary / progressive rollout so a bad release reaches 1% of users instead of 100% — staged traffic with bake times, gating metrics compared against the concurrently-running stable baseline, and automated promote-or-rollback. Use when shipping a risky change, when you want automatic rollback on regression, or when moving off all-at-once deploys.
imtiazrayhan/agentscamp-library/skills/devcontainer-designer Skill
1★ repoDesign a reproducible dev environment (Dev Container / Docker) so onboarding is one command and 'works on my machine' dies — by detecting the project's real stack and versions, authoring a devcontainer.json (+ Dockerfile/compose) that pins the runtime to what the repo targets, wires dependent services, caches dependencies, and injects secrets instead of baking them. Use when new contributors struggle to set up the project, when environment drift causes inconsistent behavior, or when standardizing tooling across a team.
imtiazrayhan/agentscamp-library/skills/dockerfile-optimizer Skill
1★ repoShrink and harden an existing Dockerfile — multi-stage builds, cache-friendly layer order, a lean pinned base image, a .dockerignore, and a non-root runtime user — without changing what the image runs. Use when an image is too large, builds are slow because the cache never hits, or a scan flags the container running as root.
imtiazrayhan/agentscamp-library/skills/feature-flag-retirer Skill
1★ repoRetire stale feature flags by confirming each flag's decided final state, then collapsing every conditional to the winning branch and deleting the loser plus the now-dead code it reached. Use when temporary flags have outlived their rollout, when flag conditionals clutter the code, or during a flag-debt cleanup.
imtiazrayhan/agentscamp-library/skills/github-actions-optimizer Skill
1★ repoMake a GitHub Actions workflow faster, cheaper, and harder to attack — by profiling where wall-clock and billed minutes actually go, then adding content-keyed caching, matrix/job parallelism, run-cancellation, and path filters, and hardening the supply chain (SHA-pinned actions, least-privilege GITHUB_TOKEN, safe fork-PR handling). Use when CI is slow or queues, when a repo burns Actions minutes, or before trusting a workflow that runs on untrusted pull requests.
imtiazrayhan/agentscamp-library/skills/release-notes-writer Skill
1★ repoWrite user-facing release notes — the curated 'what's new and what it means for you' — by starting from the real changes (git log / merged PRs / the changelog since the last release) and translating developer-speak into user impact, grouped by what the user cares about with breaking changes and required actions surfaced first. Use when shipping a release to users or customers and the raw commit log isn't something a user should read, when you need a published GitHub-release / blog / in-app announcement, or when a breaking change must be made unmissable so upgrades don't break.
imtiazrayhan/agentscamp-library/skills/runbook-writer Skill
1★ repoWrite an operational runbook a half-asleep on-call engineer can execute at 3am — scoped to ONE alert, leading with how to confirm the problem, the copy-pasteable mitigation that stops user pain, then diagnosis, escalation, and verification. Use when an alert has no documented response, after an incident exposed a missing procedure, or when standing up on-call for a service.
imtiazrayhan/agentscamp-library/skills/semver-advisor Skill
1★ repoDecide the correct semantic-version bump — major, minor, or patch — by diffing a release range, mapping the changes onto the public API surface, and classifying each as breaking, additive, or a fix. Use before cutting a release when you are unsure whether changes are breaking, when a teammate proposes a bump you want to sanity-check, or when a behavior change has no signature change and you need to know if it is still breaking.
imtiazrayhan/agentscamp-library/skills/slo-definer Skill
1★ repoTurn a vague reliability goal into concrete SLIs, SLOs, an error budget, and burn-rate alerts — service-level indicators measured at the user-facing boundary, targets over a rolling window, and a written policy for what happens when the budget runs out. Use when a service has no defined reliability target, when on-call is noisy and alert-fatigued, or before you commit to an SLA you can't measure.
gitgitWi/council-flow/skills/deploy Skill
no license1★ repoMulti-LLM Plan and TDD flow
SkillMedev/legacy-modernization/skills/language-version-migrator Skill
1★ repoPorts a codebase across a breaking language or runtime version with compatibility shims, batched automated transforms, dual-runtime CI, and old-vs-new output diffing, ending in a flag-flip cutover with a rollback rule. Use when someone says "migrate us from Python 2 to 3", "we're jumping Node majors", "move to the next Java LTS", or any runtime upgrade where source must change to keep compiling or behaving correctly. Do NOT use for an application framework's major version (React, Rails, Spring) - use framework-upgrader instead; for proving a database schema or data migration is safe, use migration-safety-checker; and skip it entirely when the runtime change is purely operational (base image, CI matrix, deploy target) with no syntax or semantic breaks.
The same file is in 1 other repository
Stepkar2004/init-configurator/.claude/skills/workflow Skill
1★ repoThe SWE loop binding every implementation session in this repo - fire whenever code is about to be written, changed, or resumed, at every chunk start and end, and whenever unsure what the next step is. Covers orient -> plan -> implement -> verify -> document -> commit (NEVER push) -> reflect. Nested lazy parts; load references/scale.md when work outgrows one context window (massive task/refactor, flood of tasks, mass research); load references/rot-check.md before a release, after a long repo gap, or on "rot check"/"is anything stale". Not for scaffolding new stacks (bootstrap) or skill hygiene (skill-manager).
Stepkar2004/init-configurator/src/init_configurator/genome/skills/workflow Skill
1★ repoThe SWE loop binding every implementation session in this repo - fire whenever code is about to be written, changed, or resumed, at every chunk start and end, and whenever unsure what the next step is. Covers orient -> plan -> implement -> verify -> document -> commit (NEVER push) -> reflect. Nested lazy parts; load references/scale.md when work outgrows one context window (massive task/refactor, flood of tasks, mass research); load references/rot-check.md before a release, after a long repo gap, or on "rot check"/"is anything stale". Not for scaffolding new stacks (bootstrap) or skill hygiene (skill-manager).