CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-creator-ms

Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services. Use when creating new skills or updating existing skills.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/skill-creator-ms/SKILL.md

The canonical home for this skill is skill-creator-ms in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 thorough, highly actionable skill-authoring guide with an excellent step-by-step workflow, explicit validation checkpoints, and concrete templates. Its main issues are length (violating its own 500-line limit), long inline templates that should live in reference files, and references/ files that are named in the body but missing from the bundle, which undermines the progressive-disclosure structure it teaches.

Suggestions

Create the referenced files (references/azure-sdk-patterns.md, references/workflows.md, references/output-patterns.md) or remove the dangling references so the bundle matches what the body promises.

Move the full acceptance-criteria template, scenarios.yaml example, and the complete example-skill markdown into references/ files, leaving only concise summaries in SKILL.md to get under the 500-line limit.

Trim meta-explanations Claude already knows (e.g., the progressive-disclosure levels and 'context window is a shared resource' rationale) to just the skill's own operational rules.

DimensionReasoningScore

Conciseness

Mostly dense, domain-specific guidance without basic-concept padding, but the ~620-line body exceeds the skill's own 'Keep SKILL.md under 500 lines' rule and could be tightened — the 60-line example skill, the acceptance-criteria template, and the full scenarios.yaml template inline content that belongs in reference files. It is not a 2 because almost every section carries non-obvious, actionable information rather than padded explanation.

3 / 5

Actionability

Guidance is largely copy-paste executable: exact symlink commands, `pnpm harness` invocations, authentication snippets in four languages, YAML scenario templates, and a final checklist. It falls short of 5 only because several code blocks use placeholder constructs (e.g., `ServiceClient(endpoint, credential)` and the generic 'Example SDK' example) that cannot run as-is, though the pattern-role of those snippets is implicitly justified.

4 / 5

Workflow Clarity

The 8-step creation process is clearly sequenced with explicit validation checkpoints: symlink verification via `ls -la`, mock-mode test runs with defined success criteria ('100% pass rate, no false positives'), and the iterative Ralph Loop (`--max-iterations 5 --threshold 85`) as a built-in feedback loop, plus a final pre-completion checklist. This matches the top anchor for clear sequence, explicit validation, and feedback loops; nothing significant is missing.

5 / 5

Progressive Disclosure

The body has good section structure and clearly signals one-level-deep references (e.g., 'See references/azure-sdk-patterns.md' and the Design Pattern References table), but the referenced files (azure-sdk-patterns.md, workflows.md, output-patterns.md) do not exist in the bundle, so the disclosure chain is broken at the top level, and large template/example content is inlined in SKILL.md instead of being split out per the skill's own guidance. It is not a 4 because content that clearly belongs in separate files is inlined and the named references are absent, and not a 2 because the in-body organization, navigation tables, and reference signaling are present and clear.

3 / 5

Total

15

/

20

Passed

Description

62%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 solid description that states both what it does and when to use it, with a clearly scoped Azure/Microsoft Foundry domain. Its main weaknesses are the thin set of trigger keywords (missing common synonyms like 'write/make a skill' or 'SKILL.md') and a 'when' clause that could name more concrete triggering scenarios.

Suggestions

Add trigger phrase variations users actually say, e.g. 'Use when writing, creating, or updating SKILL.md files, building Azure SDK skills, or adding skills to the skill catalog.'

Include the concrete artifact name 'SKILL.md' and related terms like 'skill authoring' or 'skill catalog' so the description matches natural requests and file-based triggers.

Mention one or two more specific capabilities (e.g., skill structure, test scenarios, symlink categorization) to lift specificity beyond the two generic create/update actions.

DimensionReasoningScore

Specificity

The description names the domain ("AI coding agents working with Azure SDKs and Microsoft Foundry services") and two concrete actions ("creating new skills or updating existing skills"), but offers no further specifics about what the guide covers (structure, testing, categorization), matching the anchor for domain plus 1-2 concrete actions. It is not a 4 because it does not list several specific actions, and not a 2 because 'creating' and 'updating' skills are real, concrete actions rather than generic filler.

3 / 5

Completeness

It explicitly answers both what ("Guide for creating effective skills for AI coding agents working with Azure SDKs and Microsoft Foundry services") and when ("Use when creating new skills or updating existing skills"), matching the anchor where both are present but the 'when' could be more specific. It is not a 5 because the 'when' clause lacks concrete trigger phrases or scenario elaboration; not a 3 because the 'when' is explicit, not merely implied.

4 / 5

Trigger Term Quality

Natural phrases like "creating new skills" and "updating existing skills" are present and users would say them, but common variations and synonyms are missing — e.g., 'write a skill', 'make a skill', 'SKILL.md', 'skill authoring', 'Azure SDK skill'. This matches the anchor 'some relevant keywords but missing common variations or synonyms' rather than 4, where only a few natural terms would be missing.

3 / 5

Distinctiveness Conflict Risk

The Azure SDK / Microsoft Foundry focus carves a fairly clear niche, so it is mostly distinct with only minor overlap risk against other general skill-creation or Azure-oriented skills. Not a 5 because 'creating effective skills' is a broad capability area where other skill-creator skills would compete; not a 3 because the Azure/Foundry scoping meaningfully narrows the overlap.

4 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (620 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 13 missing

Warning

Total

13

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/skill-creator-ms/SKILL.md

Reviewed

Table of Contents

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.