Skip to content

ericrisco/rsc-harness / skills/github-actions

github-actions

Verified

Use when authoring or fixing GitHub Actions CI/CD — workflows under .github/workflows, triggers, job matrix, caching, token permissions, OIDC cloud deploys, environment gates, reusable workflows. NOT the Dockerfile or image build strategy (that is `docker`), NOT the branching model (that is `git-workflow`), NOT release readiness (that is `ship`).

FileKindSize
SKILL.mdskill md13.1 KB
evals/README.mdmarkdown985 B
evals/cases.yamlconfig3.2 KB
references/caching-and-matrix.mdmarkdown3.9 KB
references/oidc-deploys.mdmarkdown4.6 KB
scripts/verify.shexecutablescript4.1 KB

evals/README.md

View on GitHub
# Evals — github-actions

`cases.yaml` is a routing-and-capability spec, not an automated test runner. Read `should_trigger` / `should_not_trigger` as a judgement set: feed each prompt to the skill router and check it lands here for the trigger cases and routes to the named sibling (docker, git-workflow, ship, deployment, vercel) for the non-trigger cases — the non-obvious ones (caching by symptom, concurrency by symptom, OIDC instead of stored keys) are the ones worth watching. For `capability`, have the agent produce the hardened CI+deploy pipeline from the scenario and score it against the `must_include` rubric — every bullet should be present (SHA-pinned third-party actions, read-only default permissions, built-in cache, version matrix, gated OIDC deploy job, tuned concurrency). To sanity-check the artifact the skill emits, run `scripts/verify.sh <repo>` against a repo containing the generated workflows; it is read-only and exits non-zero only on a hard error.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall