Individual skill

knowledge-base-integration

Use when configuring or running product-level Knowledge Ingest, target-ref Feature catalogs, Evidence Policy decisions, Revision Sets, idempotent smoke, or local/remote knowledge runners across repositories.

packages/omp-sbtd/kit/onboard/runtime/templates/skills/knowledge-base-integration/SKILL.md

Read pinned source

Source commit 0d9331bd7d64c28dea368fd4385fd009809d58da

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 195
Repository last updated: Nov 5, 2026
License: Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

LICENSEasset · 11,358 bytes
NOTICEasset · 720 bytes
SKILL.mdcore · 7,093 bytes
SKILL.mdcore · 7,093 bytes
SKILL.mdcore · 7,093 bytes
SKILL.mdcore · 7,093 bytes
references/artifact-manifest.schema.jsonasset · 1,300 bytes
references/deployment-manifest.example.yamlasset · 658 bytes
references/deployment-manifest.schema.jsonasset · 1,628 bytes
references/evidence-decision.schema.jsonasset · 2,329 bytes
references/metrics.schema.jsonasset · 861 bytes
references/product.example.yamlasset · 1,952 bytes
references/product.schema.jsonasset · 4,923 bytes
references/revision-set.schema.jsonasset · 1,240 bytes
references/runner-job.schema.jsonasset · 1,340 bytes
references/runner-result.schema.jsonasset · 1,716 bytes
references/runtime-contract.mddoc · 3,872 bytes
references/workspace.local.example.yamlasset · 790 bytes
references/workspace.schema.jsonasset · 2,497 bytes
requirements.txtdoc · 36 bytes
scripts/knowledge_base_p1.pyruns · 92,432 bytes

Read excerpt


# Knowledge Base Integration

Use this Skill for the P1 read-only integration runtime. Repository-owned `.feature` files at configured target refs remain the behavior SOT. The runtime produces rebuildable catalogs and evidence bundles; it does not change source repositories.

## Steps

1. Read the product registry and server workspace mapping. Validate both with `scripts/knowledge_base_p1.py validate-config`. Completion: every required repository has an explicit remote, role, target ref, feature root, and contained local mapping.
2. Resolve Evidence intent before a formal run with `decision`. Completion: the immutable decision records `required` / `not-required` / `blocked`, targets, source rule, reason, policy version, and digest.
3. For `read / 读取`, run `ingest`. Completion: every available ref is fixed to a full commit SHA; complete no-ID Gherkin structures, locators, bindings, conflict candidates, `metrics.json`, and `ingest-summary.json` exist; `mutation` is `none`.
4. For CI or knowledge-server smoke, run `smoke` only after runner, environment, account, data, service, device, and app-artifact prerequisites are known. Completion: staged native commands ran through the local or configured command Runner Adapter; current-run reports, Chinese summaries, artifact manifest, checksums, metrics and evidence bundle exist, or the run is explicitly `blocked`.
5. Report exact status and paths. P1 publication is always `not-configured`; PR checks, remote publication, invalidation, retention, quarantine and gates belong to P2.

## Commands