Creates a mapping matrix of literature to thesis chapters to identify coverage gaps.
Install
mkdir -p .claude/skills/map && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17250" && unzip -o skill.zip -d .claude/skills/map && rm skill.zipInstalls to .claude/skills/map
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Show or update the mapping between literature and thesis chapters — which sources support which arguments. Use for tracking coverage.Key capabilities
- →Scan literature notes for source information
- →Scan chapter files for chapter headings
- →Build a mapping matrix between sources and chapters
- →Identify chapters with insufficient source support
- →Output mapping and coverage summaries
How it works
The skill scans literature notes and chapter files to extract source and chapter information, then constructs a matrix showing which sources support which chapters. It identifies under-covered chapters based on a minimum source threshold.
Inputs & outputs
When to use map
- →Tracking literature coverage
- →Mapping sources to chapters
- →Identifying research gaps
About this skill
/map — Literature-Thesis Mapping Skill
Purpose
Build and display a mapping matrix showing which literature sources support which thesis chapters. Identify coverage gaps where chapters lack sufficient source support.
Trigger Words
This skill activates on: map, show mapping, coverage, which sources, /map.
Workflow
-
Scan all notes files in
literature/reading_notes/using Glob (*_NOTES.md). For each file, extract:- Author and title (from the
# Reading Notes:heading) Statusfield valueRelevancefield value- All rows from the
## Thesis Connectionstable
- Author and title (from the
-
Scan chapter files in
chapters/to get the list of chapters and their section headings. -
Build the mapping matrix. Rows are sources (sorted alphabetically by author), columns are chapters (Ch1 through Ch8 or however many exist).
- Mark each cell with the connection type if a mapping exists (e.g.,
supports,challenges,extends). - Leave cells empty if no connection.
- Mark each cell with the connection type if a mapping exists (e.g.,
-
Identify coverage gaps. Flag any chapter that has fewer than 3 mapped sources as "under-covered".
-
Output the mapping.
Output Format
## Literature-Thesis Mapping -- {YYYY-MM-DD}
### Matrix
| Source | Status | Ch1 | Ch2 | Ch3 | Ch4 | Ch5 | Ch6 | Ch7 | Ch8 |
|--------|--------|-----|-----|-----|-----|-----|-----|-----|-----|
| Smith (2024) | integrated | | supports | supports | | | | | |
| Jones (2021) | integrated | extends | supports | supports | extends | | | | |
| Lee (2019) | completed | | | supports | | | challenges | | challenges |
### Coverage Summary
| Chapter | Mapped Sources | Status |
|---------|---------------|--------|
| Ch1 | {N} | OK / Under-covered |
| Ch2 | {N} | OK / Under-covered |
### Under-covered Chapters
{List chapters with < 3 sources, with suggestions for which completed-but-not-yet-mapped notes might fill the gap.}
Saving the Matrix
If the user says "save" or "export mapping", write the matrix to literature/mapping_matrix.md using Edit (if the file exists) or Write (if creating new). Include a timestamp header.
Gap Threshold
- Under-covered: fewer than 3 mapped sources per chapter.
- This threshold can be adjusted if the user specifies a different minimum.
Constraints
- Read-only by default. Only modify files if the user explicitly asks to save the matrix.
- No emoji in output.
- No hardcoded chapter count. Detect chapters dynamically from the
chapters/directory. - Source names use the format
{Author} ({Year})for readability. - Connection types are derived from the
Connection Typecolumn in notes files. If that column is missing, infer from theRelevancefield.
When not to use it
- →When the user does not explicitly ask to save the matrix
- →When the user wants to modify files without explicit instruction
- →When the user wants to use emojis in the output
Limitations
- →The skill is read-only by default.
- →The output does not include emojis.
- →Source names must follow the format '{Author} ({Year})'.
How it compares
This skill automates the process of mapping literature to thesis chapters and identifying coverage gaps, providing a structured overview that would otherwise require manual tracking and analysis.
Compared to similar skills
map side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| map (this skill) | 0 | 3mo | No flags | Beginner |
| product-manager-toolkit | 32 | 7mo | Review | Beginner |
| gathering-requirements | 3 | 8mo | No flags | Intermediate |
| ideate | 1 | 6mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by yha9806
View all by yha9806 →You might also like
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
gathering-requirements
CaptainCrouton89
Systematically clarify user needs, preferences, and constraints before planning or implementation. Classifies work type, investigates existing systems, discovers edge cases and integration points, resolves assumptions, and creates detailed specifications. Use when building features, enhancements, or integrations where requirements need clarification.
ideate
liveloveapp
Capture and document a new idea in this repo. Use when the user says things like "help me brainstorm", "I have an idea", or "let's capture this for the future" and wants it recorded in `design/ideas/` with a summary, supporting research (repo context + web if useful), and a sketch.
rfc
jiangzhe
Design and resolve RFC documents through evidence-gated multi-round workflow. Use when planning large architectural/program-level changes in docs/rfcs, enforcing goal/scope/direction clarity, explicit first-principles/long-term/original-fit proposal lenses with rationale, draft-to-formal progression
gsd-map-codebase
wikiepeidia
Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
idea-extraction
RepairYourTech
Exhaustive idea extraction through recursive breadth-before-depth exploration with Deep Think protocol and fractal structure. Use during /ideate to transform raw ideas into comprehensive, structured ideation output. Writes to a fractal folder hierarchy — every node has an index, CX file, and childre