tckit: Skill for Claude Code

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

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

A research workflow for Beckhoff TwinCAT automation software and hardware documentation. Beckhoff Infosys is the manufacturer's technical reference site.

In plain words
What is it for?
Use it to look up TwinCAT functions and libraries, their inputs and outputs, timing details, and Beckhoff hardware specifications.
Why use it?
It grounds answers in the manufacturer's documentation instead of relying on possibly outdated memory about function blocks, libraries, or hardware.

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-beckhoff-docs/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-beckhoff-docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/georgeturneruk/tckit/tc-beckhoff-docs/github.svg)](https://agentmods.dev/skills/georgeturneruk/tckit/tc-beckhoff-docs)
Your own site
<a href="https://agentmods.dev/skills/georgeturneruk/tckit/tc-beckhoff-docs"><img src="https://agentmods.dev/badge/skills/georgeturneruk/tckit/tc-beckhoff-docs/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-beckhoff-docs

Your own site · 80×15
<a href="https://agentmods.dev/skills/georgeturneruk/tckit/tc-beckhoff-docs"><img src="https://agentmods.dev/badge/skills/georgeturneruk/tckit/tc-beckhoff-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 158 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 936 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.00158 $0.00936
Opus 5 $0.00079 $0.00468
Sonnet 5 $0.00032 $0.00187
Haiku 4.5 $0.00016 $0.00094

Measured 9d ago against content hash 97cee19d0d09, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

tc-beckhoff-docs 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 9d 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-beckhoff-docs/SKILL.md · 34 lines

How it starts

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

Researching Beckhoff infosys

Beckhoff FB conventions, timing notes, and hardware specs are not reliable in training data, especially for newer TF libraries and hardware. Always ground claims in infosys.

Procedure

  1. Known FB name → FindFb. If the user (or your prior reasoning) has a specific FB name, call FindFb(fbName) first. The result includes inputs, outputs, timing notes, and a description.
  2. Fuzzy query → SearchDocs. When you don't know the exact name, call SearchDocs(query, section=""). Use section to scope to a known infosys area when you know one.
  3. Hardware order number → FindHardware. For a Beckhoff hardware product (e.g. EL3004, EK1100, EPP6228-0022, EJ1100, CU1128), call FindHardware(orderNumber). It returns the product description, the infosys URL, and the parsed "Technical data" table. The order number may carry a variant suffix (EPP6228-0022); it is normalised to the bare order. Covers EtherCAT Terminals (EL/EM/ELM/ED), couplers (EK), EtherCAT Box (EP/ER/EQ), EtherCAT P Box (EPP), plug-in modules (EJ), IO-Link boxes (EPI/ERI), and infrastructure/switches (CU).
  4. Need full content → GetDocPage. If a FindFb, SearchDocs, or FindHardware snippet is insufficient, call GetDocPage(url) for the full parsed page. Pages are cached locally — re-calls are cheap.
  5. Always cite. When reporting findings, include the infosys URL so the user can verify. Do not paraphrase parameter or technical-data tables without referencing the source.
  6. Hand back. Once you have the inputs/outputs/timing/specs you need, return control to the calling skill (typically tc-write-st) with a one-line summary plus the URL.

Notes

  • Latency. The first lookup into an uncached infosys section crawls the menu tree (with a polite delay) and can take a few seconds; the result is cached, so repeat lookups are local and fast.
  • FindHardware empty technical_data. For the pure catch-all sections erxxxx (rugged) and eqxxxx (stainless steel), infosys has no per-order datasheet page, so the description and URL resolve but technical_data is []. ER/EQ boxes are the EP equivalents in a different housing — if the user needs the table, look up the matching EP order number and flag that the housing/protection differs.

Read the full file on GitHub · 34 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. 9d ago First seen · 34 lines · 158 tokens per session scan A 97cee19d0d09

Subscribe to this mod's changes

tc-beckhoff-docs is a skill published in the GitHub repository georgeturneruk/tckit (5 stars, last pushed 15d ago), licensed MIT. It adds 158 tokens to every session and 936 once invoked, about $0.0008 per session on Opus 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

Other skills, from other repositories

gke-compute-classes

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…

google/skills · 83 tokens

jetson-diagnostic

Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.

NVIDIA/skills · 30 tokens

doca-socket-relay

Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…

NVIDIA/skills · 236 tokens

offensive-z-wave

Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…

SnailSploit/Claude-Red · 113 tokens

hsb-flash

Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…

NVIDIA/skills · 94 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens