tckit: Skill for Claude Code

.claude/skills/tc-docs-write/SKILL.md

tc-docs-write is a skill for Claude Code from georgeturneruk/tckit. It costs 172 tokens per session (1,015 once invoked), scanned A, original, MIT.

A skill for writing or updating the TcKit documentation site and README. TcKit is a toolkit for TwinCAT 3 industrial-control projects.

In plain words
What is it for?
Use it to update TcKit's MkDocs pages or README when its user-facing behavior changes.
Why use it?
It helps keep documentation aligned with changes to tools, commands, settings, installation, and architecture without adding unnecessary pages.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is georgeturneruk/tckit's own configuration. It tells Claude Code how to work on tckit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tckit configures →

Reuse

Borrowing it

Nothing to install: this file belongs to georgeturneruk/tckit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/georgeturneruk/tckit/main/.claude/skills/tc-docs-write/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/georgeturneruk/tckit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for tc-docs-write

README.md
[![agentmods](https://agentmods.dev/badge/skills/georgeturneruk/tckit/tc-docs-write/github.svg)](https://agentmods.dev/skills/georgeturneruk/tckit/tc-docs-write)
Your own site
<a href="https://agentmods.dev/skills/georgeturneruk/tckit/tc-docs-write"><img src="https://agentmods.dev/badge/skills/georgeturneruk/tckit/tc-docs-write/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for tc-docs-write

Your own site · 80×15
<a href="https://agentmods.dev/skills/georgeturneruk/tckit/tc-docs-write"><img src="https://agentmods.dev/badge/skills/georgeturneruk/tckit/tc-docs-write.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 172 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,015 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00172 $0.01015
Opus 5.5 $0.00069 $0.00406
Sonnet 5.5 $0.00034 $0.00203
Haiku 4.5 $0.00017 $0.00102

Measured 2mo ago against content hash edb1048d3135, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

tc-docs-write scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/tc-docs-write/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Writing TcKit docs

The TcKit docs site lives under docs/content/ (MkDocs). The README at the repo root mirrors a slice of it. Both are user-facing surfaces and follow the same voice rules.

When to update docs

A change touches user-facing behaviour, and therefore needs a docs update in the same PR, if any of the following are true:

  • MCP tool names, arguments, or return shapes changed
  • CLI commands or flags changed
  • Config keys changed (config.json, ~/.tckit/permissions.json, .env)
  • Install or setup steps changed
  • Ports, adapters, or the one-rule architecture statement changed
  • An ADR moved to Implemented for a design decision that has now shipped

If none of those apply, the change does not need a docs update. Don't invent one.

Which surface to update

  • README — only when the surface shown on the README itself has changed. The README is a slice, not the whole story; many real-behaviour changes affect docs/content/ only.
  • docs/content/ — the default. Find the page that owns the changed surface (capability page for tool/argument changes, getting-started for install, architecture page for the one-rule statement, etc.) and edit there.

If the README and the relevant docs/content/ page both need to change, both go in the PR.

Voice rules

The home page (docs/content/index.md) takes its voice from the README. When editing the home page, match the README's structure, density, and tone. (The capability and adapter pages under docs/content/capabilities/ are denser reference material and have their own appropriate voice — don't apply this rule to them.)

For every user-facing page:

  • No ADR references. ADRs are an internal design store. docs/content/, the README, MCP tool descriptions, and CLI help text describe current behaviour, not the history of how it got there. If a passage needs more context than fits inline, link to the PR. Never link to adrs/.
  • No history paragraphs. Don't chronicle what something used to be. "The port had two more methods in an earlier draft" belongs on the ADR or in the commit message, not on a page describing the current shape.
  • No marketing scaffolding on the home page. Specifically, do not add:
    • problem/solution framing tables that repeat the capabilities list (e.g. "What TcKit solves")
    • redundant capability summaries ("X at a glance" next to a capabilities table)
    • "Design philosophy" or similar sections that duplicate the architecture page
    • feature-pitch bullet lists

Read the full file on GitHub · 65 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 65 lines · 172 tokens per session scan A edb1048d3135

Subscribe to this mod's changes

tc-docs-write is a skill published in the GitHub repository georgeturneruk/tckit (11 stars, last pushed 2mo ago), licensed MIT. It adds 172 tokens to every session and 1,015 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

tc-docs-write compared with skills from other repositories

tc-docs-write next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
tc-docs-writegeorgeturneruk/tckitSkill112mo agoMITA172Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex