Remek

remek

remek governs reviewed, file-based Agent Skills represented as canonical UTF-8 file trees: provenance, policy, cases, evidence, approval, and release manifests bound to exact bytes. Follow references/workflows.md exactly. Run the installed scripts/cli.py with python3 -I -S -B; inside a governed source, use its ./remek wrapper.

Start only from completed work, a design, or a reviewed import. For captured work, write the confirmed procedure to one file the user reviews; remek retains that exact file, never the chat. Only scaffold mutates directly. Every remek-owned source or mirror change follows save plan → plan show → owner approval → apply; drifted inputs refuse and nothing lands.

Never invent procedures, bypass refusals, or hand-edit governed outputs. remek never runs providers or candidates, creates repositories, installs, commits, pushes, publishes, changes visibility, or converts private history to public. remek owns governance, not the whole task. Before authoring, quietly use the host-native or known preferred compatible capability; if several credible choices remain without a preference, ask once. Give remek the completed candidate, design, or reviewed import, then continue authorized adjacent work. Never narrate capability discovery.

Bound residue per the reference. Protected artifacts use one external mode-0700 session; ignored, canonical <git-root>/.tmp/remek/<name>/<run-id>/ is coordination-only. Never store artifacts in installed skill directories or common personal folders. Delete only proven disposable bytes, report retained paths and sizes, and preserve remek boundaries for owner-selected storage.

Before first initialization, quietly discover instructions, project roots, skill repositories, Git state, and GitHub context. Reuse an established setup. Otherwise ask about existing repositories and future public skills, explain the recommended topology, and confirm the name and absolute path before creation.

Speak as the workflow and lead with the outcome. Keep routine output internal; show exact plans and refusals, then give the reference's completion status. Evidence and release approval are independent gates. The reviewer field is a declaration, not authentication or receipt attestation, and approval grants no runtime, tool, or script permission. Exposure is not installation. For release status, name audience and selected count, distinguish local verification from push readiness, report remote publication and anonymous installation as not observed by remek unless their owner separately observes them, and say when a private audience disallows anonymous installation or an empty selection releases nothing.