Index of every page on this site: llms.txt
All skills
hagaiw avatar

/prepare-blind-trial

@33ac0e9
Run it yourself

Prepare an isolated external repository trial using an exact target revision and the current local SkillRoll main without running inference.

  • 4 files
  • 9 KB
  • Updated 2 weeks ago
  • GitHub
Use this Skill: https://skilld.dev/gh/hagaiw/skillroll/prepare-blind-trial

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈40 tokens for metadata: the name and description. ≈487 when used: this file. ≈1.8k more on demand in 3 files.

Description uses 2.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈162 characters, or 2.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Prepare a blind trial

Create a disposable workspace from a preregistered target. Pin the target and the local SkillRoll build to exact commits, record dirty and freshness state, and install from the selected local SkillRoll checkout rather than silently substituting a published release.

Initialize SkillRoll around the repository's active skills root, validate the generated files offline, and add advisory CI only when requested. Do not run candidate repository commands, overwrite existing workflows, commit, push, publish, or expose an inference key. Preparation evidence is not a live eval. The final manifest must name generated paths and commands and explicitly state whether doctor and eval ran. Record the completed install or build from the pinned local SHA and the completed initialization of the target skills root as separate steps. If a combined setup result only reports the pins or files, obtain completion evidence before reporting either step as done.

Read preparation context for isolation, secrets, and the trial manifest.

When advisory CI is requested, open the generated workflow directly after creation, before exporting or reporting the manifest. With a generic action wrapper, use Read with the exact generated workflow file as path. For any secret-backed pull-request step or job, verify an explicit same-repository guard that excludes fork PRs; do not use pull_request_target to run fork-controlled code with secrets. Report the exact verified guard in the manifest. A preparation summary that says “verified” without showing the condition is insufficient. If direct inspection cannot verify the guard, report a blocker. For an existing workflow at the destination, report the path collision, whether the file stayed byte-for-byte unchanged, and whether its own secret boundary was verified. If only a byte comparison was authorized, report its secret boundary as unverified.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 33ac0e9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 6 days ago.

Activeupdated 2 weeks ago

README badge

README badge for hagaiw/skillroll/prepare-blind-trial