Use this skill when the user wants questions where the hard part is reading long documentation before writing code. Trigger it for requests such as “make it dig through a codebook,” “make the agent figure out what the columns mean,” “make it use survey docs first,” or “make it connect the question to the right variables from a giant manual.” Plain-language examples: “Ask something where the data is easy but the documentation is the bottleneck,” “make it find the right field definitions,” “make it read the user guide before calculating.”
[Case 1]
[Case 2]
To synthesize data for this capability, you must strictly follow a 3-phase pipeline. Do not hallucinate steps. Read the corresponding reference file for each phase sequentially:
Phase 1: Environment Exploration
Read the exploration guidelines to discover raw knowledge seeds:
references/EXPLORATION.md
Phase 2: Trajectory Selection
Once Phase 1 is complete, read the selection criteria to evaluate the trajectory:
references/SELECTION.md
Phase 3: Data Synthesis
Once a trajectory passes Phase 2, read the synthesis instructions to generate the final data:
references/SYNTHESIS.md