create-bkn

Guides creation of BKN (Business Knowledge Network) definition files following v2.0.1 spec. Covers network, object_type, relation_type, action_type, concept_group. Use when creating knowledge networks, BKN files, object types, relation types, action types, concept groups, or when user asks to model business knowledge in BKN format. When ontology-core is also loaded, use it to run ontology CLI (bkn push) after files exist.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body with excellent progressive disclosure into a real bundle (spec, templates, examples all present). Its main defects are an internal contradiction between step 10's root 'SKILL.md' and the 'Delivered BKN: root GUIDE.md' section (with a broken matching anchor), and some duplicated action_type guidance that costs tokens.

Suggestions

Resolve the step 10 contradiction: pick one filename for the delivered agent-facing guide (the section and the k8s example use GUIDE.md) and fix both the step text and the broken anchor link '#delivered-bkn-root-skillmd'.

State the action_type frontmatter rule ('action_type: add|modify|delete', in frontmatter not the Bound Object table) in one place — the validation checklist — and reference it from workflow step 11 instead of repeating the full Chinese explanation twice.

Trim version-sensitive detail: mention the spec version once ('per v2.0.1') and drop the bare restatement, or fold version notes into the SPECIFICATION reference so the body stays stable as versions change.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence (terse sections, a per-type table, no basic-concept explanations), but the action_type frontmatter rule is stated twice — in workflow step 11 and again in the validation checklist — and the bare 'v2.0.1' version reference is time-sensitive detail that costs tokens.	4 / 5
Actionability	Concrete commands ('ontology bkn validate <dir>', 'ontology bkn push <dir> [-bd <business-domain>]'), explicit naming/heading rules, build/skip/ask decision rules for actions, and real templates and examples make this mostly copy-paste executable. The step-10 instruction to create a root 'SKILL.md' contradicts the 'Delivered BKN' section's 'GUIDE.md', leaving one instruction unexecutable as written.	4 / 5
Workflow Clarity	A 13-step sequence with MUST-marked review and validation steps, a fix-and-re-run feedback loop, and a checklist would merit the top anchor, but the SKILL.md/GUIDE.md contradiction plus the broken anchor link '#delivered-bkn-root-skillmd' (the actual heading is 'root GUIDE.md') break internal coherence.	4 / 5
Progressive Disclosure	The body is a genuine overview: full rules live in references/SPECIFICATION.llm.md, templates in assets/templates/, and a complete k8s example tree in references/examples/ — all verified to exist, one reference level deep, and clearly signaled via the per-type table and inline links.	5 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concrete about the five artifact types, with an explicit and specific 'Use when...' trigger clause. The only weakness is keyword coverage stopping just short of comprehensive — the '.bkn' extension and a few synonyms are absent.

Dimension	Reasoning	Score
Specificity	Names the domain (BKN definition files) and several concrete artifacts/actions — network, object_type, relation_type, action_type, concept_group, plus running 'ontology CLI (bkn push)'. Minor gaps (e.g. validate/pull only implied) keep it below the comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both what ('Guides creation of BKN definition files... Covers network, object_type, relation_type, action_type, concept_group') and when (a 'Use when...' clause with concrete trigger phrases), matching the top anchor's pattern.	5 / 5
Trigger Term Quality	'Use when creating knowledge networks, BKN files, object types, relation types, action types, concept groups, or when user asks to model business knowledge in BKN format' covers the natural phrasings well, but misses the '.bkn' file-extension synonym users might type.	4 / 5
Distinctiveness Conflict Risk	BKN is a clear niche with domain-specific triggers ('BKN format', 'knowledge networks', 'ontology-core'); overlap risk with other skills is minimal.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 12 deeper-than-1-level	Warning
referenced_paths_exist	Referenced path issues: 24 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: UnicomAI/wanwu
Path: configs/microservice/bff-service/configs/agent-skills/ontology/create-bkn/SKILL.md
Commit: a16301c

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.