Mapping skills
The six skills that produced the evaluation. They are Claude Code skills: each SKILL.md is a written procedure the model follows, so the mapping process is inspectable and re-runnable rather than a one-off prompt.
The skills are non-deterministic: running one twice can produce different verdicts. That is why verify-analysis exists, and why every mapping in the evaluation is published in both its automated and its reviewed form.
The pipeline
extract-codebases-from-paper paper -> tools + codebases
|
v
codebase-map / docs-map tool -> analysis + colour profile
|
v
verify-analysis reconciles repeated runs
|
v
merge-profiles per-tool profiles -> union profile
refresh-feature-model-infos sits outside this chain: it runs whenever the feature model changes, to keep the files that describe it in step.
The skills
extract-codebases-from-paperGiven a paper, identifies the tools it discusses and, for each one, searches for its codebase or documentation URL. Codebases found are downloaded automatically; missing ones are recorded for a manual lookup. Particularly useful for papers that compare several tools, and it copes with broken or outdated links by falling back to a web search.
codebase-mapGiven the codebase of a tool, maps it onto the feature model and produces three artifacts: a human-readable report, an analysis document, and a colour profile. The analysis mirrors the structure of the feature model, one bullet per leaf feature, and every finding must cite at least one
file:linereference so the mapping can be verified independently.docs-mapMirrors
codebase-mapfor tools that are not open source. It takes a documentation URL instead of a local path and cites documentation links rather thanfile:linereferences as evidence, producing the same three artifacts.verify-analysisReconciles several runs of the mapping skills, which are non-deterministic and may differ in results, evidence, and conclusions. It inspects the different versions of a tool's mapping and, where they disagree, re-examines the evidence to determine the best-supported conclusion. When that is still inconclusive the feature is marked inconclusive and left for the user to decide.
merge-profilesCombines the per-tool colour profiles into a union profile showing what a chosen set of tools covers together. With no arguments it merges every analysed tool; given a paper it merges only that paper's tools; given tool names it merges just those.
refresh-feature-model-infosChecks whether the files that depend on the feature model are still in sync with it, reports any discrepancies, and updates them once approved.
Shared references
Two files the mapping skills read. They are identical wherever they appear, so they are listed once here rather than repeated per skill. refresh-feature-model-infos is what keeps every copy in sync with the model.
| File | What it is | Size |
|---|---|---|
feature-model-dimensions.md | The feature model's dimensions, as the skills consume them | 5 KB |
analysis-template.md | The blank analysis document each mapping fills in | 2 KB |