024-context-mapping

Use when a problem under exploration needs its surrounding system context identified before design begins — Existing systems, Integrations, Ownership, and External dependencies. This should trigger when an issue's Context Mapping point of view needs evaluation, or when a maintainer directly asks to map the systems, integrations, owners, and external dependencies relevant to a problem. Part of Plinth Toolkit

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/024-context-mapping/SKILL.md

Quality

Content

72%

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

The body is concise and well-structured with excellent progressive disclosure via a real one-level reference file. Its weaknesses are workflow validation checkpoints and in-body actionability, both of which defer concrete detail to the reference rather than embedding it.

Suggestions

Add an explicit validation/feedback step in the Workflow (e.g. after step 4, verify each item is evidenced or explicitly flagged as unclear before reporting).

Include one short worked example inline (e.g. a sample Existing-systems/Integrations/Ownership block) so the guidance is actionable without opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence, and avoids explaining concepts it already knows — every line (Constraints, When to use, Workflow, Reference) earns its place, matching the "Lean and efficient; every token earns its place" anchor.	3 / 3
Actionability	It gives concrete, specific guidance (name owners, identify data-flow direction, flag gaps) but provides no executable artifacts or worked examples inline — all detail is deferred to the reference file — so it sits between abstract description and copy-paste-ready instruction.	2 / 3
Workflow Clarity	The six-step Workflow is clearly sequenced, but it lacks explicit validation/feedback checkpoints beyond a final "flag any item left open" step; per the rubric, missing validation steps in a process cap this at 2 rather than 3.	2 / 3
Progressive Disclosure	The SKILL.md is a concise overview with a single, clearly signaled one-level-deep reference to references/024-context-mapping.md (a real file in the bundle), and content is appropriately split rather than inlined, matching the "Clear overview with well-signaled one-level-deep references" anchor.	3 / 3
	Total	10 / 12 Passed

Description

85%

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 is concrete, complete, and distinctive, with explicit "Use when" triggers and a well-scoped pre-design niche. Its only weak point is trigger-term naturalness, where some jargon ("point of view needs evaluation") is less likely to match a user's own wording.

Suggestions

Replace the jargon-heavy trigger "when an issue's Context Mapping point of view needs evaluation" with phrasings a user would naturally say, e.g. "when you need to map the systems and integrations around a problem."

Dimension	Reasoning	Score
Specificity	The description lists concrete actions and a named domain — "Existing systems, Integrations, Ownership, and External dependencies" — which match the "Lists multiple specific concrete actions" anchor rather than the vague level-1 or partial level-2 examples.	3 / 3
Completeness	It answers both what (identifying surrounding system context before design) and when via an explicit "Use when a problem under exploration needs..." clause plus a maintainer-request trigger, matching the both-what-and-when anchor.	3 / 3
Trigger Term Quality	It includes some natural phrasings ("map the systems, integrations, owners, and external dependencies") but leans on jargon like "Context Mapping point of view needs evaluation," which a user would rarely say verbatim, so it falls short of the full natural-term coverage anchor.	2 / 3
Distinctiveness Conflict Risk	It carves a clear pre-design niche (context mapping before a system boundary is assumed) and ties it to a specific toolkit, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/024-context-mapping/SKILL.md
Commit: 26b0e71

Reviewed: about 20 hours ago

Table of Contents

Discovery Implementation Validation

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.