Skip to content
Agentmart
Submit a tool

meta-gh-cicd

Disposable meta-skill (delete after the harness is built): turns a GitHub-hosted project's local quality checks into GitHub Actions workflows that gate pull…

Skill by minato-ellie-archive

IndexedApache-2.0
Write a review

Chalk Labs

Need help deploying meta-gh-cicd?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/minato-ellie-archive-meta-gh-cicd

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Disposable meta-skill (delete after the harness is built): turns a GitHub-hosted project's local quality checks into GitHub Actions workflows that gate pull requests — CI mirrors the commands developers and agents already run locally, with workflow syntax, action versions, and runner capabilities always fetched live from the Actions docs, never recalled from memory. Use when a harness build on a GitHub repository must add or restructure CI. Not for choosing which linters or tests the project runs (CI mirrors checks that already exist), and not for merge protections or release automation — those are separate concerns of the harness.

Use cases: devops, productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/meta-gh-cicd

What's inside

Skill name
meta-gh-cicd
Description
Disposable meta-skill (delete after the harness is built): turns a GitHub-hosted project's local quality checks into GitHub Actions workflows that gate pull requests — CI mirrors the commands developers and agents already run locally, with workflow syntax, action versions, and runner capabilities always fetched live from the Actions docs, never recalled from memory. Use when a harness build on a GitHub repository must add or restructure CI. Not for choosing which linters or tests the project runs (CI mirrors checks that already exist), and not for merge protections or release automation — those are separate concerns of the harness.
License
Apache-2.0
Instructions
57 lines in SKILL.md · view on GitHub

Files (6)

  • SKILL.md
  • agents-md-cicd.md · assets/
  • checks.yml · assets/
  • docs-navigation.md · references/
  • monorepo-paths.md · references/
  • slow-checks.md · references/

SKILL.md (first lines)

# GitHub Actions as the Quality Gate

This skill produces a pull-request-gating workflow that runs exactly the
project's existing local checks, plus an AGENTS.md section mapping every
CI job to the local command that reproduces it. It expects a repository
whose origin remote is GitHub and whose local checks (test, lint,
format, type) already exist and pass.

## Workflow

1. Inventory the local gates: task-runner recipes, git hooks, and the
   test, lint, format, and type-check commands the project actually
   runs. CI mirrors these; a check with no local equivalent is a design
   smell to raise with the user, never to add silently.
2. Assess `.github/workflows/` — existing working workflows stay. Note
   their job and check names: platform protections elsewhere in the
   harness key on those names, so renames are breaking changes.
3. Read [docs-navigation.md](references/docs-navigation.md) before the
   session's first fetch from docs.github.com, or when any recorded URL
   no longer resolves. Fetch current workflow syntax, trigger semantics,
   and the default token permissions from
   <https://docs.github.com/en/actions> before writing any YAML.
4. Agree the gate design with the user: which checks run on pull
   requests, on pushes to the default branch, and on a schedule; which
   are required versus advisory; and a runtime budget for the required
   set.
5. Copy [checks.yml](assets/checks.yml) to
   `.github/workflows/checks.yml` and rework every line: each job runs
   the project's real local command verbatim, the permissions block is
   minimal and explicit, and third-party actions are referenced the way
   the fetched docs currently recommend.
6. Read [monorepo-paths.md](references/monorepo-paths.md) when the
   repository hosts more than one independently checked package or app.
   Read [slow-checks.md](references/slow-checks.md) when any required
   check would exceed the agreed runtime budget.
7. Copy [agents-md-cicd.md](assets/agents-md-cicd.md) into the target's
   AGENTS.md and rework it — it states the CI-to-local command mapping
   and how to reproduce any CI failure locally. This deposit is what
   future agents keep after this skill is deleted.

Done when: a pull-request-triggered workflow runs exactly the project's
local check commands and passes on the current tree, and AGENTS.md maps
every CI job to the local command that reproduces it.

## Gotchas

- Entry points only: never record versioned, deep, or `latest`-pinned
  URLs — details are fetched from the entry point at use time.
- Never deploy a canned workflow: action references, runner labels, and
  syntax are fetched live this session — a remembered action version may
  already be stale or unmaintained.
- CI that checks what local hooks don't (or the reverse) trains everyone
  to ignore one of them — one command set, two runners.
- Keep required checks inside the runtime budget; anything expensive or
  hardware-bound runs on a schedule or on demand, never as a PR gate.

From minato-ellie-archive/meta-skills, Apache-2.0.

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Jul 23, 2026 (3 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get meta-gh-cicd running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying meta-gh-cicd?

CallGet help
Cite this page

meta-gh-cicd skill. Agent Mart. https://agentmart.dev/skills/minato-ellie-archive-meta-gh-cicd (last updated 2026-10-24)