fusion-code-conventions

Applies and explains code conventions across TypeScript, React, C#, and Markdown. Enforces naming rules, file naming patterns, TSDoc and XML doc standards, inline comment intent (the *why*, not the *what*), code structure, error handling, async patterns, and dead code policy. Also enforces ADR and contributor doc decisions, and flags decisions that appear stale or misaligned with current tooling. USE FOR: convention questions, code review against project standards, applying naming rules, auditing intent comments, checking TSDoc completeness, enforcing recorded ADR decisions, and flagging stale architectural decisions. DO NOT USE FOR: security vulnerability scanning, performance profiling, runtime debugging, or generating net-new code without a review target.

Quality

85%

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 orchestration skill with concrete routing, real one-level-deep references, and validation checkpoints that respect its mutating nature. Tightening the slight redundancy between the precedence and safety sections would push conciseness higher.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean: tables, bullet lists, and routing rules with no padding about concepts Claude already knows. Minor repetition (precedence rules restated in Safety & constraints) keeps it just below the leanest anchor.	4 / 5
Actionability	Concrete routing by file extension, named agent files, authoritative reference paths, and a Required/Recommended/Advisory output taxonomy give executable guidance; as an orchestration skill it lacks inline code, which is appropriate, leaving only minor gaps.	4 / 5
Workflow Clarity	A clear four-step sequence (Classify/route, Apply/explain, Present findings, Apply corrections) with validation checkpoints ('ask before proceeding', 'only corrections the user explicitly approves'). It is a mutating skill but includes explicit confirmation, so it is not capped at 3.	4 / 5
Progressive Disclosure	SKILL.md is an overview pointing one level deep to real, verified reference files (references/.conventions.md, assets/.follow-up.md) that exist on disk, with clearly signaled navigation and no nested-reference chains.	5 / 5
	Total	17 / 20 Passed

Description

92%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, specific description that concretely enumerates capabilities, gives explicit use/non-use triggers, and draws clear boundaries against adjacent skills. The only minor gap is the absence of file-extension synonyms in the trigger list.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across four languages plus cross-cutting concerns: 'Enforces naming rules, file naming patterns, TSDoc and XML doc standards, inline comment intent... code structure, error handling, async patterns, and dead code policy', and 'flags decisions that appear stale'.	5 / 5
Completeness	It explicitly answers both what ('Applies and explains code conventions...') and when ('USE FOR: ...') with concrete trigger phrases, and adds a DO NOT USE FOR boundary, matching the top anchor.	5 / 5
Trigger Term Quality	The USE FOR clause gives natural trigger phrases ('convention questions', 'code review against project standards', 'auditing intent comments', 'flagging stale architectural decisions'), but it omits file extensions and a few synonyms, so it sits just below the comprehensive-synonym anchor.	4 / 5
Distinctiveness Conflict Risk	A clear niche (multi-language convention enforcement plus ADR/constitution) with explicit DO NOT USE FOR boundaries against security, performance, debugging, and code-gen skills, minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: equinor/fusion-framework
Path: .agents/skills/fusion-code-conventions/SKILL.md
Commit: 5b70066

Reviewed: 2 days 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.