factory-environment-setup SKILL.md skillA
factory-environment-setup from curie-eng/curie is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add curie-eng/curie/factory-environment-setup@git:20261029.4f5db2cPins git:20261029.4f5db2c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- curie-eng/curie
- Path
tests/vectors/factory-skills-v1/factory-environment-setup/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261029.4f5db2c, committed Oct 29, 2026
- Size
- 4,353 bytes
- Repository stars
- 48
- License
- Apache-2.0
Plan, review, build, and deploy a repository-specific Software Factory sandbox image using repository history and verification requirements. Use during factory setup or when onboarding another repository.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Set up a factory repository environment Work for one configured factory repository binding at a time. The repository's code host and issue tracker are separate identities: GitHub and GitLab may serve both roles; Jira Cloud supplies issues for a GitHub or Bitbucket Cloud/DC code host. Follow the actual binding. Do not infer a tracker from a repository URL, or treat an inaccessible history as evidence that no tools are needed. Use the configured provider's read interface: GitHub issues and pull requests; GitLab issues and merge requests; Jira Cloud issues plus the linked code-host pull requests; or Bitbucket Cloud/DC pull requests plus the bound Jira issues. Preserve host and project identity when linking records. Ask for missing read access rather than substituting another provider's history. ## Prepare a reviewable plan 1. Identify the binding, factory agent, code host, tracker, base branch, current runner image digest, and operator-owned Helm values. Read-only access is sufficient for planning. Keep private repository and deployment identifiers out of public upstream records. 2. Read the repository's verification declaration, CI workflows, manifests, …
Read the whole file at its exact version.
How to install
mdr add curie-eng/curie/factory-environment-setup@sha256:4ba53e7f4ad5eebdThe line at the top of this page pins the label git:20261029.4f5db2c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_foqemdy7qnxs3n7b)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 29, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4353 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
curie-eng/curie · 48 stars · license Apache-2.0 · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_foqemdy7qnxs3n7b GET https://markdownregistry.com/api/v1/resolve?ref=curie-eng/curie/factory-environment-setup GET https://markdownregistry.com/api/v1/blob/4ba53e7f4ad5eebd415708ad3affde15bd5648f52c0cb2db13cdae7d7cfcae07
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.