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

74%

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

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.

The body is well-structured with clear progressive disclosure to one real reference file and a sequenced workflow with flagging checkpoints. It is held back by triple restatement of the four core items and by the absence of inline worked examples, which would otherwise make the guidance more directly executable.

Suggestions

Collapse the redundant restatements: keep the four items in either the 'What is covered' list or the 'Constraints' MUST list, and have the Workflow reference them rather than re-listing each.

Inline one short worked example or an output template (e.g. a sample Existing-systems/Integrations/Ownership/External-dependencies block) so the body is actionable without requiring a round-trip to the reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude's intelligence, but the same four items (systems, integrations, ownership, external dependencies) are restated across the 'What is covered', 'Constraints' MUST list, and 'Workflow' sections, creating noticeable redundancy.	3 / 5
Actionability	Guidance is concrete and procedural with explicit MUST/MUST NOT rules, but the body itself contains no worked examples or output templates — those live only in the reference — leaving the inline guidance instructive but not fully copy-paste executable.	3 / 5
Workflow Clarity	A clear 6-step numbered sequence is present, and Step 6 plus the 'MUST NOT invent... flag the gap' rule provide an explicit flagging/validation checkpoint; only minor validation detail is implicit.	4 / 5
Progressive Disclosure	The body is a concise overview with a single, well-signaled one-level-deep reference (references/024-context-mapping.md, which exists) linked in a dedicated Reference section, making navigation easy.	5 / 5
	Total	15 / 20 Passed

Description

85%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 is specific, complete, and clearly distinguishable, explicitly stating both what the skill does and when to trigger it. Trigger-term quality is the weakest dimension because the phrasing is somewhat formal/jargon-heavy and omits more colloquial user phrasings.

Suggestions

Add a few natural, user-spoken trigger phrases (e.g. 'map the systems and integrations around this issue', 'who owns the systems involved here') alongside the formal 'Context Mapping point of view' wording.

Consider including everyday synonyms such as 'system map', 'dependency map', or 'ownership map' to broaden natural-term coverage.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'identify existing systems', 'Mapping integrations and data flows', 'Naming ownership', 'Identifying external dependencies (third-party services, other teams, contracts)' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	It explicitly answers both what ('Guide identification of Existing systems, Integrations, Ownership, and External dependencies') and when ('Use when a problem under exploration needs its surrounding system context identified before design begins... when a maintainer directly asks to map...'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Trigger phrases are domain-specific but lean technical ('Context Mapping point of view', 'Functional Specification lenses'); common natural variations a user would say (e.g. 'map the systems around this problem') are present in the body but weaker in the description itself.	3 / 5
Distinctiveness Conflict Risk	It occupies a clear niche — pre-design context mapping for a Functional Specification — with distinct triggers ('before design begins', 'Context Mapping point of view') and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 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: f6dfc6f

Reviewed: about 2 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.