Installing the Teamcenter skills in Claude Code

Everything in this Developer section is generated from a library of Claude Code skills. Reading them here is useful; installing them is what makes Claude apply them automatically whenever you do Teamcenter work — it will reach for the right recipe without being told which one.

What a skill actually does

A skill is a markdown file with a name and a description. Claude Code reads only the descriptions until a task looks relevant, then loads the full skill. So installing sixteen skills costs almost nothing until one is needed.

The practical effect: ask for a Teamcenter object to be created and Claude already knows that createItems faults where createAttachAndSubmitObjects works, that a 200 OK with an empty result usually means a wrong payload shape rather than a dead operation, and that it must re-read the object before telling you it exists.

Install (recommended)

The library is a Claude Code plugin marketplace. The repo is private, so ask Chris for access to chrisdamonmartini/tc-automation-skills first.

Then, in Claude Code:

/plugin marketplace add chrisdamonmartini/tc-automation-skills

/plugin install tc-automation-skills@tc-automation

Restart Claude Code. To pull later updates:

/plugin marketplace update tc-automation

Install without GitHub access

Copy the repo anywhere on disk, then point Claude Code at the folder:

/plugin marketplace add ./path/to/tc-automation-skills

Or skip plugins entirely and drop the skills straight into a skills directory — ~/.claude/skills/ for every project, or .claude/skills/ inside one project:

mklink /J .claude\skills path\to\tc-automation-skills\skills

A junction (Windows, no admin needed) or a symlink keeps one source of truth and avoids the copies drifting apart.

Verifying it took

Ask Claude something that should trigger one, for example "connect to Teamcenter and list the workflow handlers registered on the tier". If the skills are loaded it will use tc-soa-session for the connection and tc-workflow-authoring for the handler lookup, rather than improvising a login.

What you still need separately

The skills are knowledge, not credentials or connectivity. To actually run against a tier you also need:

• network reach to a Teamcenter web tier, and an account on it;
• the tc MCP server if you want the tc_* tools rather than hand-rolled HTTP — the skills work either way, but the tooling path is faster;
• for the offline WSDL lookup (scripts/soa_lookup.py), a local Help Server installation to index. Without it the rest of the library still works; you just lose the "what are this operation's required members" answer.

A note on trust

Every recipe in this library was run against a live Teamcenter tier and read back before it was written down, or is explicitly marked as documented-but-unproven. That distinction is deliberate and is the most valuable thing here — Teamcenter returns HTTP 200 on faults and on deprecated no-ops alike, so "it did not error" proves nothing. If a page does not say something was verified, assume it was not.