CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

technical-articles

Technical articles and blog posts with honest trade-offs. Use when: "write a blog post", "draft an article", "write about this", creating articles in docs/articles/.

Quality

72%

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 ./.agents/skills/technical-articles/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 strong, opinionated writing-conventions skill whose paired good/bad examples and quantified rules make it genuinely actionable despite having no code. Its weaknesses are redundancy (the no-template rule and good/bad lists restate earlier sections) and a single 230-line file where specialized material like the transcript-voice guidance could be split into references.

Suggestions

Merge the Constraints no-template rule with the Articles Have Different Shapes section, and collapse the What Makes Articles Good/Bad lists into the sections that already state each rule, cutting roughly 30-40 lines of duplication.

Move the specialized "When the User Gave You the Voice" transcript-handling section (and optionally the good/bad example catalog) into a references/ file, keeping SKILL.md as a concise overview with a clearly signaled link.

Add an ordered final-pass checklist (opening → rhythm → headings → punctuation → closing) so the general article case has the same explicit sequence the architecture-article workflow already has.

DimensionReasoningScore

Conciseness

The body is genuinely opinionated guidance with concrete good/bad pairs rather than pedagogical padding, but at ~230 lines it repeats itself: "Don't follow a single template. Structure should fit the content" appears in both Constraints and Articles Have Different Shapes, and the What Makes Articles Good/Bad bullet lists restate rules already given in Writing the Opening, Visual Elements, and Constraints. This fits anchor 3 (mostly efficient but could be tightened) rather than 4, where redundancy would be only minor.

3 / 5

Actionability

For an instruction-only skill the guidance is highly actionable: quantified rules ("Max 3-4 sentences of prose before a code block", "max 1-2 of each [list] per article", "core code transformation... lands in the first ~100 words") and paired good/bad examples for titles, headings, openings, voice, and explanatory prose. It stops short of anchor 5 because a few directives stay abstract — "build the private model" and "Preserve the article's altitude" never get a concrete worked shape, and the linked AGENTS.md conventions are assumed rather than summarized.

4 / 5

Workflow Clarity

The Architecture Article Composition section gives a clear 3-step sequence (build private model → turn into public argument → apply conventions and punctuation pass), and the voice section supplies a usable self-test ("would the user, skimming their own article a week later, feel the impetus"). This matches anchor 4 (clear sequence, most checkpoints) rather than 5: the general article case has no ordered drafting/checking sequence, and the architecture workflow has no validation or revision loop.

4 / 5

Progressive Disclosure

The file has clear, well-named section headings and its one external pointer (AGENTS.md writing conventions) is clearly signaled, but the entire ~230-line body is inline with no bundle files at all — the transcript-voice section and the good/bad example catalogs are self-contained chunks that could live in reference files. Since this is far beyond the under-50-line single-file exception and content that could be separate is inline, it fits anchor 3 rather than 4.

3 / 5

Total

14

/

20

Passed

Description

70%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 with an explicit and natural "Use when" clause containing realistic user phrases. Its main weakness is that the capability statement is a verbless noun phrase, so what the skill actually does (write, structure, edit articles) must be inferred from the triggers rather than read directly.

Suggestions

Lead the description with an explicit third-person verb phrase, e.g. "Writes and edits technical articles and blog posts with honest trade-offs", so the capability is stated rather than implied by triggers.

Add one or two distinct capability verbs beyond writing (e.g. structuring, editing drafts, preserving author voice) to broaden coverage and sharpen the what-statement.

DimensionReasoningScore

Specificity

The capability statement "Technical articles and blog posts with honest trade-offs" is a noun phrase with no verbs; the only concrete actions ("write a blog post", "draft an article", "creating articles in docs/articles/") appear inside the trigger clause and all describe the same single action of writing articles. This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4, which requires several distinct actions like extract/fill/merge.

3 / 5

Completeness

Both elements are present: the "what" ("Technical articles and blog posts with honest trade-offs") and an explicit, specific "when" ("Use when: 'write a blog post', 'draft an article'..."). Not score 5 because the "what" is a fragment rather than a clear capability statement — it never says the skill writes, edits, or structures articles.

4 / 5

Trigger Term Quality

The quoted triggers "write a blog post", "draft an article", and "write about this" are phrases a user would naturally say, and "docs/articles/" adds a path-based trigger. It falls short of anchor 5 because common synonyms like "publish a post", "technical writing", or "blogging" are missing.

4 / 5

Distinctiveness Conflict Risk

The technical-articles focus, the docs/articles/ path, and the quoted phrases give it a clear niche with minor overlap risk against general writing or documentation skills — "write about this" is broad enough to collide with other writing tasks. This fits anchor 4 rather than 5, and is well above anchor 3's generic overlap risk.

4 / 5

Total

15

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

EpicenterHQ/epicenter

Path

.agents/skills/technical-articles/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.