CtrlK
BlogDocsLog inGet started
Tessl Logo

infographics

Use when generating Basic Memory PR, changelog, release, or weekly images from Codex.

56

Quality

65%

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

Quality

Content

67%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.

The body is a well-structured, largely executable workflow guide with real one-level references and explicit verification steps. Its main weaknesses are repetition of the same image-form and copyright guidance across sections, the absence of the referenced scripts/ files from the bundle, and the inlined style-category pool that should live in its own reference file.

Suggestions

Deduplicate the repeated image-form list and copyright warnings — state them once (e.g. in the Aesthetic Contract) and reference that section elsewhere, cutting roughly 20 lines.

Move the BM category pool into a reference file (e.g. references/bm-style-categories.md) and keep only the selection rules in SKILL.md.

Add concrete commands for the changelog/weekly evidence-gathering step (e.g. git log / git diff --stat invocations) so those modes are as executable as PR mode.

DimensionReasoningScore

Conciseness

The ~70-line BM category pool is project-specific knowledge Claude would not know and earns its place, but the image-form list ("poster, scene, tableau, cover, painting, photograph, staged artifact") is restated four to five times across PR Mode, Style Selection, the Aesthetic Contract, and Quality Bar, and the copyright and 'not a text-heavy infographic' warnings are each repeated. Mostly useful with several redundant restatements fits anchor 3, not the minor-trim level of 4.

3 / 5

Actionability

PR mode supplies fully-specified executable commands (gh pr view with --jq, uv run with every flag, --print-prompt dry-run) and the theme/provenance marker blocks are concrete. Falls short of 5 because the cited scripts/generate_pr_infographic.py and scripts/generate_infographic.py are absent from the bundle, and changelog/weekly modes give no commands for assembling the diff evidence (e.g. no git diff invocation).

4 / 5

Workflow Clarity

PR mode is clearly sequenced with a pre-spend local prompt test and a "Verify the image exists and is readable before reporting success" checkpoint, matching the clear-sequence-most-checkpoints anchor. Not 5 because changelog and weekly modes are unordered checklists with no numbered steps or explicit validation of the evidence pack before generation.

4 / 5

Progressive Disclosure

Sections are well-organized, and both body references (references/prompt-blueprint.md, references/style-balance.md) exist in the bundle and are one level deep and clearly signaled ("Read these references before drafting the prompt"). Not 5 because the large BM category pool is inlined in SKILL.md — content that clearly belongs in a reference file, which the rubric treats as inlining rather than appropriate splitting.

4 / 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.

The description has a clear explicit trigger and a distinct niche, but says almost nothing about what the skill actually does beyond 'generate images' — the entire PR-fetch/script-run/evidence-pack workflow is invisible, and natural trigger synonyms are missing. It reads as a when-clause with an embedded minimal what, not a full what+when statement.

Suggestions

State the 'what' concretely before the trigger: e.g. "Fetches the PR body, builds an evidence pack of merged changes, and generates editorial images via the BM infographic scripts".

Add natural trigger synonyms users would say, such as "infographic", "release-notes image", "weekly retro image", or "PR visual".

Drop or explain the "from Codex" jargon — a user describing their need would not say it, and it obscures the skill's scope.

DimensionReasoningScore

Specificity

"generating Basic Memory PR, changelog, release, or weekly images" names the domain and artifact types but describes only one concrete action (generating images). It is not the entirely-vague anchor 2, and it lacks the several distinct actions needed for anchor 4.

3 / 5

Completeness

The explicit "Use when generating…" clause answers 'when' clearly, and 'what' is stated (image generation for four named artifact types), matching the both-present-but-could-be-more-explicit anchor. It is not a 5 because the 'what' is thin: nothing about fetching PR bodies, running generator scripts, evidence packs, or style selection, and not a 3 because 'when' is explicit rather than missing or implied.

4 / 5

Trigger Term Quality

Covers "PR, changelog, release, weekly images" but omits natural variations users would say ("infographic", "visual", "release-notes image", "PR summary image") and leans on jargon ("from Codex") that a user would not naturally utter. Fits the 'some relevant keywords, missing common variations' anchor rather than the 'good coverage' anchor 4.

3 / 5

Distinctiveness Conflict Risk

Triggers are niche ("Basic Memory PR, changelog, release, or weekly images") and unlikely to fire for unrelated skills, fitting the mostly-distinct anchor 4. It is not a 5: "images" alone overlaps with general image-generation skills, and "from Codex" muddies the niche boundary.

4 / 5

Total

14

/

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

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
basicmachines-co/basic-memory
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.