BF asset-graph-management
Build, maintain, validate, and publish an evidence-backed asset graph or OKF-style resource map for operations, ops, DevOps, SRE, platform engineering, infrastructure inventory, CMDB-like service catalogs, dependency mapping, incident handoff, and 运维 discovery. Use when mapping operational assets such as repositories, compute, services, databases, queues, websites, pipelines, storage, networks, identity systems, MCP servers, Jenkins/CI jobs, APIs, external services, or business systems; when a user provides an entrypoint or config such as SSH, URL/API, MCP, Jenkins, Git, database, object storage, cloud, Kubernetes, monitoring, or SaaS access and expects discovery; when turning scattered operational knowledge into agent-readable Markdown plus structured frontmatter; or when preparing open-source/demo-safe asset-management methodology without exposing private infrastructure.
Build, maintain, validate, and publish an evidence-backed asset graph or OKF-style resource map for operations, ops, DevOps, SRE, platform engineering…
As a process F 30/100 · Will not run — References files that are not bundled: references/asset-model.md, references/devops-discovery.md, references/evidence-and-safety.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/asset-model.md - warning
missing-refreference to a missing file: references/devops-discovery.md - warning
missing-refreference to a missing file: references/evidence-and-safety.md - warning
missing-refreference to a missing file: references/script-requirements.md - warning
missing-refreference to a missing file: references/publishing-checklist.md
Process rating: all ten parameters 30/100
- 0Tools and files. 5 referenced file(s) missing: references/asset-model.md, references/devops-discovery.md, references/evidence-and-safety.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (asset-graph-management) differs from the folder (okf-asset-graph)
- 100Steps. 15 steps
- 100Execution cost. Instruction body is 1084 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 885: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 7 headings
- +3Step-by-step instructions: 15 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.