agentsclimarketplace

Setup repo

Skill mblauberg/provenant/skills/setup-repo

Portable equal-primary Claude and Codex agent harness for a governed agentic SDLC

Install
npx -y skills add mblauberg/provenant --skill setup-repo

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 29 days oldThe repository was created 29 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when asked to set up or scaffold a repository's process, labels, tracker, branch ruleset, issue forms, docs layout, work-item runbook, or board. Not for this repo's own day-to-day GitHub mechanics; use its runbook.

SKILL.md

3.6 KB, 819 tokens by cl100k_base, as published. Nobody here has run it

Setup

User gate first

Before any write, user approves a plan naming the target, the exact keep/create/adapt/conflict diff and, for GitHub, the Project board. Confirm permission. Ask for an unnamed target; never infer it from cwd.

Inspect and classify

Inventory MAINTAINING.md, docs layout, .github/**, the work-item runbook and board. Classify each action as keep (exact match), create (absent), adapt (compatible; propose the merge) or conflict (semantic mismatch; STOP and ask). Never overwrite; amend the declarations block per heading. A re-run against an already-set-up repository must produce no diff.

Choose tracker

Ask: Use GitHub issues? If yes, use the GitHub branch, confirming the remote host before any gh command. If no, record the chosen tracker or none; skip labels, ruleset, issue forms and board. Tracker-specific setup remains out of scope: a documented skip, not alternate-tracker scaffolding.

Declare repository process

Amend the fixed-heading Repository process block in target MAINTAINING.md, creating it if absent, from templates/repo-declarations.md. Record the tracker choice, docs-layout homes, merge policy/authority and work-item runbook pointer. Use pointers only; never duplicate runbook or policy content. This block, not the GitHub scaffolding, is the completion gate.

Docs layout

Ask where specs, runbooks and ADRs live. Defaults: reference engineering-docs's Default homes table by skill name; do not invoke it. setup-repo owns the declaration.

GitHub branch: steps 1-7

Only when the tracker is GitHub issues and the remote host is confirmed:

  1. Labels: copy templates/labels.yml and templates/workflows-labels.yml to .github/labels.yml and .github/workflows/labels.yml; warn that skip-delete: false prunes undeclared labels.
  2. Ruleset: add the ci-status aggregate, then create the ruleset per ruleset guidance, confirming its app id.
  3. Issue forms/security: copy templates/SECURITY.md to the root, or verify existing policy has a valid private route. Copy templates/ISSUE_TEMPLATE/*.yml to .github/ISSUE_TEMPLATE/; adapt gate wording and replace owner/repo. Confirm private vulnerability reporting is enabled, or replace <private-reporting-route> with a working confidential contact method. Publish only when the placeholder is gone and both routes work.
  4. PR template: copy templates/pull_request_template.md into .github/ and adapt evidence rows; retain decision and review sections.
  5. Work-item runbook: copy the doctrine into the target, adding its mechanics; the project decides merge authority.
  6. Project board: create the six-status board.
  7. CODEOWNERS/Dependabot: adapt to the stack; the Dependabot template keeps its dependency label.

Stop conditions

Stop for an unnamed target, unconfirmed write permission, an unconfirmed remote host before any gh command, replacement of an existing ruleset or labels file, semantic conflict, or ambiguous ci-status dependencies. Ask which jobs it should needs:.

What ships with it: 15 files

27.8 KB alongside SKILL.md

evals/

references/

templates/

Gives 0 of the 12 instructions most project setup skills give in 819 tokens

Counted across 999 of the 1,637 authors here whose files we hold, read 2026-08-07

  • Ask one question at a timein 29 of 999, across 28 files
  • Detect the package manager from lockfilesin 28 of 999, across 9 files
  • Present findings to the userin 26 of 999, across 5 files
  • Explore current repo statein 24 of 999, across 3 files
  • Update the agent skills block in place if it existsin 24 of 999, across 3 files
  • Install husky lint-staged and prettierin 23 of 999, across 4 files
  • Create the lintstagedrc filein 22 of 999, across 3 files
  • Commit all changed filesin 22 of 999, across 3 files
  • Run lint-staged to verify it worksin 22 of 999, across 3 files
  • Create the husky pre-commit filein 21 of 999, across 2 files
  • Create a prettierrc file if missingin 21 of 999, across 2 files
  • Initialize huskyin 21 of 999, across 2 files

Said here and by no other author read

  • ask for an unnamed target
  • classify each action as keep, create, adapt, or conflict
  • ask whether to use GitHub issues
  • amend the repository process block in MAINTAINING.md
  • record the tracker choice and process declarations
  • ask where specs, runbooks, and ADRs live

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.