CtrlK
BlogDocsLog inGet started
Tessl Logo

using-and-extending-gdi-plus

Instructions for using GDI, GDI+ for drawing primitives, shapes and processing/rendering bitmaps and rendering Fonts. Also, tenets for adding new APIs to System.Drawing for modernization and improving drawing, imaging, and font features.

67

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/using-and-extending-gdi-plus/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

The body is highly actionable and well-sequenced with concrete, executable C# examples and a verification checklist, but it is a monolithic single file with no progressive disclosure to separate reference materials.

Suggestions

Move the detailed 'Adding New Drawing Primitives' pattern (section 5) into a references/ file, leaving a concise summary with a clearly signaled link in SKILL.md.

Extract the complete examples (section 6) to a separate examples reference to reduce redundancy with the inline patterns in sections 1–4.

Add a short quick-reference table of cached-scope APIs and the quality settings that must be restored, so the core rules are scannable without reading every section.

DimensionReasoningScore

Conciseness

Lean, rule-driven prose with concrete code and no padding about basic GDI+ concepts; every section earns its place, and the section 6 integration examples only mildly re-derive earlier patterns while adding value.

3 / 3

Actionability

Copy-paste-ready C# examples with specific APIs (GetCachedPenScope, GraphicsInternal), version guards, and integer/float overload patterns appear throughout, matching the fully-executable anchor.

3 / 3

Workflow Clarity

Section 5 sequences the new-API process across clear sub-steps (5.1–5.6) and section 7 provides a pre-submit checklist that acts as an explicit verification gate for the complex process.

3 / 3

Progressive Disclosure

Content is well-organized into sections but entirely monolithic — all ~400 lines are inline with no one-level-deep reference files, and the substantial new-API pattern in section 5 is content that could be split out.

2 / 3

Total

11

/

12

Passed

Description

67%

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

The description conveys a specific GDI+/System.Drawing niche with concrete actions, but lacks an explicit 'Use when...' trigger clause and relies on fairly technical jargon over natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when drawing with GDI+ in WinForms, rendering bitmaps or fonts, or adding new APIs to System.Drawing.'

Soften jargon with user-natural terms (e.g., 'draw shapes', 'render images/bitmaps', 'add drawing APIs') alongside the technical GDI+ vocabulary to improve trigger-term quality.

Trim redundancy between 'drawing primitives, shapes' and 'improving drawing, imaging, and font features' to tighten the description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'drawing primitives, shapes', 'processing/rendering bitmaps', 'rendering Fonts', and 'adding new APIs to System.Drawing' — rather than vague language, matching the multiple-specific-actions anchor.

3 / 3

Completeness

It clearly states what the skill does, but provides no 'Use when...' clause or equivalent explicit trigger guidance for when to invoke it, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

Domain terms like GDI+, drawing, bitmaps, and fonts are relevant but lean technical; it lacks the natural phrasings and common variations a user would actually say, falling short of full trigger coverage.

2 / 3

Distinctiveness Conflict Risk

The GDI+/System.Drawing niche is specific and unlikely to trigger for unrelated skills; it is not generic enough to conflict broadly, though the body notes overlap with sibling WinForms skills.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
dotnet/winforms
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.