operator-profile SKILL.md skillA
operator-profile from tmusser/ai-engineering-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tmusser/ai-engineering-skills/operator-profile@git:20261005.a4c4424Pins git:20261005.a4c4424 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tmusser/ai-engineering-skills
- Path
skills/operator-profile/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261005.a4c4424, committed Oct 5, 2026
- Size
- 5,594 bytes
- Repository stars
- 6
- License
- MIT
Create a compact operator preference profile that tunes safe workflow defaults without overriding task contracts, repository instructions, safety boundaries, or required verification.
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
# Operator Profile ## Purpose Configure how AI Engineering Skills should behave for a particular operator without turning personal preferences into a second task contract. Setup skill, not a workflow stage. Run it when preferences are first established or materially change, then let other skills consume the profile as a default. The profile may narrow authority; it may not grant new authority. ## When to use Use when the operator wants recurring defaults for ceremony, autonomy, verification depth, communication density, or ambiguity handling. Do not run it for every task. Skip it when the current request already gives the needed preferences or when no persistent personalization is useful. ## Inputs - Explicit operator preferences - Optional existing native user/project instructions - Optional project-specific preferences - Intended profile scope: session, project, or user Do not infer durable preferences from one-off behavior, a single terse request, or temporary task pressure. ## Authority boundary An operator profile is a preference layer, not an authorization layer. A current explicit instruction, repository-native instruction, task contract, …
Read the whole file at its exact version.
How to install
mdr add tmusser/ai-engineering-skills/operator-profile@sha256:b91591cc2c418b28The line at the top of this page pins the label git:20261005.a4c4424, 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_rjws2esj3m4k5kka)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 5, 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 (5594 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
tmusser/ai-engineering-skills · 6 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rjws2esj3m4k5kka GET https://markdownregistry.com/api/v1/resolve?ref=tmusser/ai-engineering-skills/operator-profile GET https://markdownregistry.com/api/v1/blob/b91591cc2c418b2898e08102cc89e83a6546fe52b6e0d269457c60416a0e94d6
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.