CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

push-code-snippets

Extracts inline code blocks from an input .NET documentation article file into article-relative ./snippets/ files and compilable projects. Use when moving fenced C#, Visual Basic, or XAML examples out of Markdown, adding :::code references and snippet markers, or converting embedded samples to standalone snippet projects.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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, actionable workflow with concrete commands, markers, and validation. The main gaps are a missing fix-retry feedback loop and minor redundancy in the mistakes section.

Suggestions

Add an explicit feedback loop in step 7 (e.g., 'If dotnet build fails, fix the snippet and rebuild before continuing') to strengthen workflow clarity for this batch/rewrite operation.

Trim redundancy between the inline workflow guidance and the 'Avoid Common Mistakes' section, or repurpose the latter purely as a quick checklist of failure modes not already stated.

Consider noting common validation failures and their fixes (e.g., mismatched marker identifiers, missing dev_langs entries) to make the verification step more self-correcting.

DimensionReasoningScore

Conciseness

Largely lean and assumes Claude's competence with the dotnet CLI and project scaffolding, though the 'Avoid Common Mistakes' section restates guidance already implied earlier.

4 / 5

Actionability

Provides fully executable guidance: concrete dotnet commands with flags, marker comment syntax for C#/VB, :::code reference syntax with worked examples, and a frontmatter yml snippet.

5 / 5

Workflow Clarity

A clear 7-step sequence with an explicit validation step (build, run, verify paths/identifiers, report) and a mistake checklist, but it lacks an explicit fix-and-retry feedback loop on validation failure.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and one clearly signaled one-level reference (the create-snippet-folders skill); no bundle files exist, so the single-file structure is appropriate with minor organization gaps.

4 / 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 with concrete actions and an explicit trigger clause in third-person voice. Minor keyword synonym/extension coverage is the only gap.

DimensionReasoningScore

Specificity

Lists multiple concrete actions—extracting inline code blocks into article-relative ./snippets/ files and compilable projects, adding :::code references and snippet markers, and converting embedded samples to standalone projects—giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what it does (extract inline blocks into snippet files and projects) and when to use it via a concrete 'Use when moving fenced C#, Visual Basic, or XAML examples...' clause.

5 / 5

Trigger Term Quality

Includes natural terms users would say (.NET, C#, Visual Basic, XAML, Markdown, :::code references, snippet markers) but is missing some synonyms and file extensions like .cs/.vb.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow .NET documentation snippet-extraction niche with highly specific triggers, making overlap with other skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

dotnet/docs

Path

.github/skills/push-code-snippets/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.