Use to add or audit GitHub Actions CI gates in any portfolio repo. Detects existing workflows before suggesting changes. Generates copy-pasteable YAML per stack class (A/B/C/D/E). Includes cost guardrails (Firestore Emulator only, never live), secret-name conventions, and the per-PR vs per-merge split. Keywords: GitHub Actions, CI, CI/CD, workflow, lint, test, build, deploy, gate, secrets, Firebase Emulator, cost guardrail, PR check.
EnglishUse when adding Claude-powered automation to GitHub Actions, cron jobs, or any unattended pipeline in a portfolio repo. Wraps the Claude Code SDK (claude -p --output-format json) as a "super-intelligent Unix utility" — fed via stdin or args, returns structured JSON, can be piped/jq'd/scripted. Use cases - issue triage and labeling, Sentry/error-tracking digest, log spike summarization, release notes generation, Resend/Stripe webhook event classification, the CastHub1 self-heal 3-tier escalation, weekly portfolio digest. Includes cost guardrails (per-run token budget, model selection), failure-mode handling (timeout, retry, partial output), and the standard GitHub Actions secret pattern (ANTHROPICAPIKEY). Keywords - claude -p, Claude Code SDK, headless Claude, agentic CI, GitHub Action Claude, label-issues, error-summary, log analysis, release notes, headless, unattended, automation, stdin, jq, structured output.
EnglishUse when configuring or auditing a Firebase Hosting deployment for a Vite/React SPA. Covers SPA rewrite rules, asset cache headers, Content-Security-Policy, X-Frame-Options, HSTS, Referrer-Policy, and Permissions-Policy. Especially relevant when adding a new app, hardening an existing one, or fixing CSP-induced auth/Stripe failures. Keywords: firebase.json, hosting, CSP, Content-Security-Policy, cache-control, X-Frame-Options, HSTS, SPA rewrite, security headers, Vite, React.
EnglishUse BEFORE adopting any new paid SaaS vendor or backend service in any portfolio repo. Defaults to the house stack (a single, shared set of vendors used across all 23 apps) to avoid subscription fragmentation. When a different vendor is genuinely better, requires a written pros/cons + 3-year cost projection + in-house alternative analysis BEFORE wiring anything. Companion to vendor-onboarding-walkthrough (which handles the HOW after the WHETHER is decided). Keywords: vendor, SaaS, subscription, consolidation, cost, monthly, pricing, in-house, self-hosted, Sentry, Stripe, Resend, Twilio, Supabase, Vercel, Railway, vendor sprawl, evaluation, ADR.
EnglishIncludes CI Gate Builder, Claude SDK in CI, Firebase Hosting Security, and other workflows.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
CI Gate Builder
Use to add or audit GitHub Actions CI gates in any portfolio repo. Detects existing workflows before suggesting changes. Generates copy-pasteable YAML per stack class (A/B/C/D/E). Includes cost guardrails (Firestore Emulator only, never live), secret-name conventions, and the per-PR vs per-merge split. Keywords: GitHub Actions, CI, CI/CD, workflow, lint, test, build, deploy, gate, secrets, Firebase Emulator, cost guardrail, PR check.
Claude SDK in CI
Use when adding Claude-powered automation to GitHub Actions, cron jobs, or any unattended pipeline in a portfolio repo. Wraps the Claude Code SDK (claude -p --output-format json) as a "super-intelligent Unix utility" — fed via stdin or args, returns structured JSON, can be piped/jq'd/scripted. Use cases - issue triage and labeling, Sentry/error-tracking digest, log spike summarization, release notes generation, Resend/Stripe webhook event classification, the CastHub1 self-heal 3-tier escalation, weekly portfolio digest. Includes cost guardrails (per-run token budget, model selection), failure-mode handling (timeout, retry, partial output), and the standard GitHub Actions secret pattern (ANTHROPICAPIKEY). Keywords - claude -p, Claude Code SDK, headless Claude, agentic CI, GitHub Action Claude, label-issues, error-summary, log analysis, release notes, headless, unattended, automation, stdin, jq, structured output.
Firebase Hosting Security
Use when configuring or auditing a Firebase Hosting deployment for a Vite/React SPA. Covers SPA rewrite rules, asset cache headers, Content-Security-Policy, X-Frame-Options, HSTS, Referrer-Policy, and Permissions-Policy. Especially relevant when adding a new app, hardening an existing one, or fixing CSP-induced auth/Stripe failures. Keywords: firebase.json, hosting, CSP, Content-Security-Policy, cache-control, X-Frame-Options, HSTS, SPA rewrite, security headers, Vite, React.
Vendor Consolidation Policy
Use BEFORE adopting any new paid SaaS vendor or backend service in any portfolio repo. Defaults to the house stack (a single, shared set of vendors used across all 23 apps) to avoid subscription fragmentation. When a different vendor is genuinely better, requires a written pros/cons + 3-year cost projection + in-house alternative analysis BEFORE wiring anything. Companion to vendor-onboarding-walkthrough (which handles the HOW after the WHETHER is decided). Keywords: vendor, SaaS, subscription, consolidation, cost, monthly, pricing, in-house, self-hosted, Sentry, Stripe, Resend, Twilio, Supabase, Vercel, Railway, vendor sprawl, evaluation, ADR.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the CI Gate Builder skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- License details are not provided in these listings. Check the author’s terms before using the skills.