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.
Why is this API v2 query dropping results after I add a relation?
The skills support API queries, automation diagnosis, entity-view configuration, integrations, imports, formulas, and governed change planning in active Targetprocess environments.
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.
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.
Load the right context, not the whole manual
Each compact SKILL.md routes a task to only the relevant
reference files. The agent gets focused detail without flooding its
context window with unrelated product areas.
Keep answers traceable
Every detailed reference retains the exact IBM source URLs used to build it.
Work safely in production
Permissions, tenant metadata, version gates, and write boundaries are explicit guardrails—not afterthoughts.
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-
01
AUTHORITATIVE INPUTOfficial IBM documentation
Product concepts, procedures, limitations, fields, and troubleshooting guidance.
-
02
REUSABLE KNOWLEDGE LAYERTask routers + narrow references
Non-obvious constraints, exact routing, production guardrails, and retained provenance.
-
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.
Administration, extension, integration, and API guidance for active Targetprocess environments.
Focused expertise across the data, model, reporting, administration, and deployment layers.
Plan setup, cost modeling, forecasting, collaboration, integration, and administration guidance.
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.
git clone https://github.com/SantiaGoMode/apptio-skills-registry.gitclaude --plugin-dir ./apptio-skills-registry
kiro-cli chatKiro: /context show
Claude: /apptio-skills-registry:tp-governance
Kiro: /tp-governanceCopilot 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.
- 1Generate
Build one product pack or all three.
- 2Upload
Add the flat documents to a Copilot Notebook.
- 3Ask
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