standards-to-tooling SKILL.md skillB
standards-to-tooling from pantheon-org/tekhne is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pantheon-org/tekhne/standards-to-tooling@git:20260711.6d8d5c4Pins git:20260711.6d8d5c4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pantheon-org/tekhne
- Path
skills/software-engineering/standards-to-tooling/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260711.6d8d5c4, committed Jul 11, 2026
- Size
- 8,546 bytes
- Repository stars
- 10
- License
- MIT
Translates project coding standards into concrete linting and formatting tool configurations. Given human-readable conventions (from AGENTS.md, code review guidelines, or team standards), this skill produces ESLint, Prettier, Biome, TypeScript, and other tool configs that enforce them automatically. Covers discovery, mapping, implementation, verification, and CI integration.
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
# Standards to Tooling Maps project-specific coding conventions to linting/formatting tool configuration. For the Stars project: JS/TS/Vue codebase with ESLint 10 + Prettier, migrating to full TypeScript. ## Mindset A convention that cannot be auto-enforced will drift. Before implementing any standard, always ask: *Can a tool catch this?* If yes, configure it. If no, document it as a code review checklist item. Prefer tools that provide fix-on-save or `--fix` support — adoption is higher when enforcement is automatic rather than manual. ## When to Use - Onboarding a new project and need to set up linting/formatting from scratch - Adding a new code convention that should be machine-enforced - Reviewing a PR where a convention was violated and a tool should catch it - Migrating a codebase (e.g., JS → TS) and need to update or add tooling - Standardising tooling across multiple projects or monorepo workspaces ## Workflow ### 1. Discovery — Extract actionable standards Source the project's conventions from: | Source | What to look for | |--------|-----------------| | `AGENTS.md` | Naming, import style, component conventions, file structure | …
Read the whole file at its exact version.
How to install
mdr add pantheon-org/tekhne/standards-to-tooling@sha256:62e7f3a55fa50980The line at the top of this page pins the label git:20260711.6d8d5c4, 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_x4qyqpnixrjmxtrp)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 11, 2026.
Audit of the latest version
- fail: No script tag (matched: <script)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8546 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
pantheon-org/tekhne · 10 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_x4qyqpnixrjmxtrp GET https://markdownregistry.com/api/v1/resolve?ref=pantheon-org/tekhne/standards-to-tooling GET https://markdownregistry.com/api/v1/blob/62e7f3a55fa5098002adc53f87c4af0cbabdd27a13f1bb1a98a3a931a2c7b05d
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.