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

88%

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

85%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.

The body is well-structured and actionable: a numbered workflow with mandatory validation gates, a checklist, and clean one-level-deep references to a complete bundle. Its only real weakness is moderate redundancy around the action_type frontmatter rule, which inflates token cost without adding clarity.

Suggestions

Consolidate the action_type frontmatter rule (currently restated in workflow steps 7, 11, and the Validation checklist) into a single canonical statement and reference it from the other locations to save tokens.

Replace the prose 'generate a fresh UUID v4 (e.g. Python uuid.uuid4())' with a one-line copy-paste snippet so the id-generation step is fully executable.

Make template usage concrete by showing the frontmatter skeleton of one template inline (e.g. object_type) rather than only linking the template directory.

Dimension	Reasoning	Score
Conciseness	Largely lean and assumes Claude's competence (directory layout, naming rules, brief per-type table), but the action_type frontmatter warning is repeated three times (workflow step 7/11, checklist) in near-identical Chinese prose, which could be consolidated.	4 / 5
Actionability	Provides executable commands ('ontology bkn validate <dir>', 'ontology bkn push <dir> [-bd <business-domain>]', 'uuid.uuid4()') plus a concrete directory layout and template pointers, but the UUID generation is described rather than given as a copy-paste snippet and template 'copy/adapt' guidance is slightly abstract.	4 / 5
Workflow Clarity	A 13-step sequence with explicit '(MUST)' validation and review checkpoints, a dedicated Validation checklist, and feedback loops (fix IDs/cross-refs then re-run validate before push), satisfying the destructive/batch validation requirement.	5 / 5
Progressive Disclosure	Clear overview that points one level deep to real, well-signaled references (SPECIFICATION.llm.md, assets/templates/, references/examples/k8s-network/, GUIDE.md), all of which exist in the bundle; bulk detail is appropriately externalized.	5 / 5
	Total	18 / 20 Passed

Description

91%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: it states concrete authoring targets, gives comprehensive user-facing trigger phrasing, and explicitly covers both what the skill does and when to use it. The only weakness is a slight overlap risk with the companion ontology-core skill, which it addresses but does not fully eliminate.

Dimension	Reasoning	Score
Specificity	Lists several concrete creation targets (network, object_type, relation_type, action_type, concept_group) tied to the v2.0.1 spec, but stops short of enumerating the full set of authoring actions per type, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' ('Guides creation of BKN definition files following v2.0.1 spec. Covers...') and 'when' ('Use when creating... or when user asks to model business knowledge in BKN format') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-language triggers including synonyms and format tokens ('knowledge networks, BKN files, object types, relation types, action types, concept groups, model business knowledge in BKN format') that users would naturally say.	5 / 5
Distinctiveness Conflict Risk	The BKN-specific niche is clear and unlikely to misfire, but 'knowledge networks' / 'ontology-core' boundary carries minor overlap risk; the description mitigates this by stating 'When ontology-core is also loaded, use it to run ontology CLI (bkn push)'.	4 / 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: 030c20b

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.