SkillAgentSearch skills...

setup-local-e2e-repo

Mint throwaway local repositories that look like an adopter's, for end-to-end runs of markdown-harness

Install / Use

npx skills add hancrafted/markdown-harness --skill setup-local-e2e-repo

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

56/100

Category

Automation

Supported Platforms

Universal

Our assessment of setup-local-e2e-repo

setup-local-e2e-repo scores 56/100 on our quality scale, 2699th of 2,790 Automation skills we index.

Its SKILL.md is 5.5 KB long, split into 4 sections with 2 code examples: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
14/20
Description
12/15
Adoption
0/20
Freshness
5/15

Maintenance, license and trust

  • We could not determine when the repository was last updated.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-15. Automated pattern scan on 2026-11-15. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

setup-local-e2e-repo compared with similar skills

All 4 of these similar skills score higher than setup-local-e2e-repo; compare them before choosing.

SkillScoreStarsUpdatedFormat
setup-local-e2e-repo (this skill)by hancrafted560—SKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install setup-local-e2e-repo?
Run npx skills add hancrafted/markdown-harness --skill setup-local-e2e-repo. The install tabs above show the steps for each supported agent.
Which AI agents does setup-local-e2e-repo work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is setup-local-e2e-repo safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is setup-local-e2e-repo still maintained?
We could not determine when the repository was last updated.

name: setup-local-e2e-repo description: Mint throwaway local repositories that look like an adopter's, for end-to-end runs of markdown-harness. Use when testing the markdown-harness skill from a user's point of view, reproducing a first-run experience, checking that the init or demo workflow works on a clean tree, or preparing repositories for a workshop.

An end-to-end run answers one question: does someone meeting this tool for the first time get where they are going? That only holds on a repository with no history of our fixes — so these are minted fresh and thrown away, never recycled.

1. Decide what the run is proving

The judgement, and it decides everything downstream. Ask before minting anything:

| Question | Why it changes the run | | ------------------------------------- | ----------------------------------------------------------------------------------- | | Local checkout, or published tarball? | A checkout tests unreleased work; the tarball tests what an adopter actually gets | | One repository, or several? | Several only earn their cost when comparing different starting states | | Does it need the dev-tooling harness? | It supplies the verify script init extends — skip it and init creates one instead |

Default to the published tarball unless testing something unreleased. A run against a local checkout can pass on code nobody can install yet, which is the one result that misleads rather than informs.

Done when you can say what a pass would prove and what it would not.

2. Mint the repositories

node .agents/skills/setup-local-e2e-repo/scripts/new-repo.mjs --name wiki-a,wiki-b

| Flag | Effect | | ---------------- | -------------------------------------------------------------------- | | --name | Required. Repeatable, and comma-separated — one repository per name | | --under | Where they land. Defaults to ~/Developer/mh-e2e | | --source | published (default), or a path to a local checkout to link instead | | --skip-harness | Skips @hancrafted/typescript-ai-harness, much the slowest step | | --dry-run | Reports the names and paths it would mint, and creates nothing |

Mint a comparison run's repositories in ONE invocation rather than one command each. Four hand-typed invocations differ in the ways a hand differs — a flag remembered for three of them and not the fourth — and that difference becomes a variable in the thing you are measuring.

It refuses to touch a directory that already exists. That is deliberate: a half-recycled repository is the one thing that makes an end-to-end result untrustworthy, and reusing one has produced false passes before. The refusal is per name: a stale wiki-c is reported as its own failed entry and the other three still mint, so one leftover directory does not cost a whole comparison run. Use --dry-run to see which paths are already taken before spending the installs.

It reports JSON — one entry per repository, each minted one carrying the next command to continue with. Every repository is minted even if an earlier one failed, and every step runs even after an earlier step failed, so the report says which repositories are usable and why rather than where the run stopped.

Read the provenance block. Every repository carries one, so a missing block is a bug rather than a quiet pass. On a published run the package comes from npm at its released version while the skill comes from the default branch, so the two agree only while that branch sits on the release tag. When they disagree the script says so and still succeeds: the pairing is real, no adopter can install it, and a run measured on it looks green while proving nothing. Release first, or switch to --source <checkout> and say that is what you did.

checked and drift are separate fields because "compared and equal" and "never compared" are different answers that a bare drift: false cannot tell apart. checked: false — an unreachable remote, or a version with no release tag yet — means the pairing is unverified, not that it is sound.

Done when every repository reports "ok": true, and every provenance block reports "checked": true with "drift": false. Any other combination is a result you have to explain before the run counts.

3. Hand over to the tool's own skill

From here the markdown-harness skill drives, exactly as it would for an adopter — this skill's job is finished once a clean tree exists. Open a session in the new repository and let it read the state itself rather than telling it what you just built.

The run to reproduce a genuine first encounter is: state probe, init.md, then demo.md.

The hook check needs a fresh session, not a resumed one. --continue and --resume replay saved context instead of re-running hooks, so a resumed session shows a freshness notice from a hook that never fired. That fakes a pass, and it is the single easiest way to get a wrong answer out of this.

Done when a fresh session reports the stale demo file as stale without being prompted.

4. Throw them away

rm -rf ~/Developer/mh-e2e/wiki-a

Delete them when the run is done rather than keeping them for next time. The next run's value comes from the tree being untouched, and a kept repository quietly stops being one.

Done when the directory is gone, and anything learned is recorded somewhere that is not the repository.

Related Skills

View on GitHub
GitHub Stars0
CategoryAutomation
UpdatedNaNy ago
Forks0

Trust signals

68/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

2 medium1 low