tov-guidelines SKILL.md skillA
tov-guidelines from matteotitta/repo-structure-in-house is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add matteotitta/repo-structure-in-house/tov-guidelines@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- matteotitta/repo-structure-in-house
- Path
.claude/skills/tov-guidelines/SKILL.md- Versions recorded
- 6
- Latest version
- v1.0.0, committed Oct 21, 2026
- First version recorded
- Apr 4, 2026
- Size
- 5,500 bytes
- Repository stars
- 66
- License
- MIT
Extracts a company's tone of voice from its own content and turns it into rules a writer or an AI can follow. Phase 1 analyses 15 to 20 pages for sentence, paragraph, word and structure patterns with frequency counts; after the user reviews it, Phase 2 writes the guidelines: tone attributes with before and after examples, a We are / We are not table, tone by context, vocabulary to use and avoid, and open questions. Triggers: "tone of voice", "brand voice", "voice guidelines…
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
# TOV guidelines Find out how a company actually writes, then write that down as rules specific enough that a new writer, or an AI, sounds like them on the first draft. Two phases with a review in between: first the evidence, then the guidelines. ## When to use it - Building the context folder, before any copy or content work. - Starting a content program, or onboarding writers or AI tools. - When content has drifted, or the existing guide is more than six months old. Don't use it for colours and fonts (`/brand-kit`), for what to say (`/messaging`), or when the user only wants a one-line description of the voice. ## Inputs **Required:** the company website URL. It needs a homepage and at least 5 to 10 pages of real content. If it's thin, say so and flag the sample size in the output. **Optional:** founder notes or transcripts, an existing style guide to update, `context/icp/` for the reader, `context/expert-pov/` for the founder's own voice. **Paths.** Write `context/brand/MMYY-tov-analysis.md` (Phase 1) and `context/brand/MMYY-tov-guidelines.md` (Phase 2). Agency or consultant? Swap `context/` for `clients/<client>/context/` throughout. …
Read the whole file at its exact version.
How to install
mdr add matteotitta/repo-structure-in-house/tov-guidelines@sha256:28f159e42eca53a3The line at the top of this page pins the label v1.0.0, 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_ei6f5jvaq4x334p2)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Apr 4, 2026 and Oct 21, 2026, about one every 40 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-10-21 | 6fe510a | 5,500 B | A | view · diff |
| v1.0.0 | 2026-10-21 | 99f5fe0 | 5,530 B | A | view · diff |
| v1.0.0 | 2026-10-14 | 4016985 | 5,446 B | A | view · diff |
| v1.0 | 2026-05-19 | 245a7e5 | 4,973 B | A | view · diff |
| v2.1 | 2026-04-09 | 30ae916 | 31,347 B | A | view · diff |
| v2.1 | 2026-04-04 | 50cb476 | 31,066 B | A | view |
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 (5500 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
matteotitta/repo-structure-in-house · 66 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ei6f5jvaq4x334p2 GET https://markdownregistry.com/api/v1/resolve?ref=matteotitta/repo-structure-in-house/tov-guidelines GET https://markdownregistry.com/api/v1/blob/28f159e42eca53a38e70703fd3ad95ee8a25d14566ac238c025409cf6070fa43
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.