Reusable product knowledge for AI

Give AI the context administrators actually need.

Thirty-six focused skills turn official IBM documentation into practical guidance for Targetprocess, TBM Studio, and Planning—ready for Claude Code, Kiro, or a Copilot Notebook knowledge pack.

36task-focused skills
167source-linked references
3IBM product registries
Registry routing Ready
ADMIN QUESTION

Why is this API v2 query dropping results after I add a relation?

S
SKILL ROUTERtp-rest-api-v2
matched
R
FOCUSED REFERENCEquery-language.md
loaded
Answer grounded in IBM documentation Source retained ↗
IN PRODUCTION
Used by Targetprocess administrators for real operational work.

The skills support API queries, automation diagnosis, entity-view configuration, integrations, imports, formulas, and governed change planning in active Targetprocess environments.

Admin-tested pattern

Lower the technical barrier

Help analysts troubleshoot with confidence—without asking them to become backend engineers.

Start with the symptom an analyst already recognizes: missing data, a failed automation, an unexpected calculation, or a report that no longer looks right. The skills turn it into a guided diagnostic path, explain what each check proves, favor safe read-only checks, and make clear when an administrator or engineer should take over.

Describe the symptom Follow guided checks Escalate with evidence

Why a skill registry

Documentation becomes usable working context.

A large documentation portal answers “what exists.” The registry adds the routing, constraints, and verification steps an agent needs to help with the task in front of you.

02

Keep answers traceable

Every detailed reference retains the exact IBM source URLs used to build it.

03

Work safely in production

Permissions, tenant metadata, version gates, and write boundaries are explicit guardrails—not afterthoughts.

04

Reuse the pattern

A packaged command surveys another IBM docs tree and builds a consistent new registry without duplicating the architecture.

One canonical source

Write the knowledge once. Deliver it three ways.

The repository keeps one maintainable Markdown source tree. Portable skill packages serve Claude Code and Kiro, while flat Word documents prepare the same knowledge for retrieval in a Copilot Notebook.

See the notebook workflow
  1. 01
    AUTHORITATIVE INPUTOfficial IBM documentation

    Product concepts, procedures, limitations, fields, and troubleshooting guidance.

  2. 02
    REUSABLE KNOWLEDGE LAYERTask routers + narrow references

    Non-obvious constraints, exact routing, production guardrails, and retained provenance.

  3. 03
    DELIVERYClaude Code · Kiro · Copilot Notebook

    Use the interface that fits the team while keeping the product registries canonical.

Current registry

Thirty-six skills across three products.

Browse by product. Each skill represents a coherent job an administrator, analyst, or builder can hand to an AI agent.

Claude Code + Kiro

Install once. Ask for the work in plain language.

The Claude manifest and Kiro workspace package expose all three registries. Product prefixes keep skills distinct, while either agent selects the relevant router from your request.

One repository delivers all 36 skills to Claude Code and Kiro.
01
GET THE REGISTRY
git clone https://github.com/SantiaGoMode/apptio-skills-registry.git
02
START YOUR AGENT
claude --plugin-dir ./apptio-skills-registry
kiro-cli chat
03
VERIFY, INVOKE, OR LET THE AGENT ROUTE
Kiro: /context show
Claude: /apptio-skills-registry:tp-governance
Kiro: /tp-governance

Copilot Notebook-ready RAG

Turn the registry into a retrieval-ready knowledge pack.

Copilot Notebooks need uploadable source files, not a nested skill tree. The included builder converts every router and reference into a flat, styled .docx set while preserving provenance and rewriting links so the documents still connect.

203generated documents
0duplicate source trees
COPILOT KNOWLEDGE PACK.DOCX
  1. 1
    Generate

    Build one product pack or all three.

  2. 2
    Upload

    Add the flat documents to a Copilot Notebook.

  3. 3
    Ask

    Retrieve product guidance with source context close at hand.

$ python3 tools/build_notebook_docs.py --list
$ python3 tools/build_notebook_docs.py tp
$ python3 tools/build_notebook_docs.py all

Generated folders are ignored by Git; the Markdown registry remains the canonical source.

Extend the pattern

Build the next product registry from its documentation.

The packaged command inventories an IBM docs tree, decomposes it into coherent tasks, writes source-linked routers and references, verifies coverage, builds the notebook pack, and wires the new registry into the plugin.

/apptio-skills-registry:new-skill-registry \
  <ibm-docs-root-url> <short-name> [skill-prefix]
Read the authoring playbook
OPEN SOURCE KNOWLEDGE INFRASTRUCTURE

Start with a skill. Reuse the system.

Explore on GitHub