CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-material-scout

Research and triage learning materials; read and explain sources for "请你读" / "精读"; process "素材:" intakes and "读完" closure. Explicit reading follows the source's argument, not career or project ranking.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/research-material-scout/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 skill shows strong workflow discipline — numbered sequences, explicit verification gates, and a self-verification checklist — and its bundle references are real and well-integrated. It is dragged down by substantial redundancy (triple-listed paper lanes, duplicated lifecycle rules) and by keeping ~130 lines of paper-search detail inline in an already long SKILL.md instead of a reference file.

Suggestions

Keep one canonical list of paper/preprint lanes (e.g. in a references/paper-search-lanes.md) and reference it from Paper Radar, Multi-Source Mesh, and Active Research instead of repeating it three times.

Move the arXiv route, Paper Radar Pattern, and Multi-Source Mesh sections (~130 lines) into a reference file, leaving a short pointer plus the script command in SKILL.md.

Bundle or inline the essential steps of the managed intake (the content of .local/material-lifecycle/README.md and the usage of material_wave_ranking.py) so the core intake workflow is executable without files absent from the skill.

DimensionReasoningScore

Conciseness

The body is noticeably padded: the venue/preprint lane list (NeurIPS, ICLR, ICML, ACL, EMNLP, AAAA, bioRxiv, medRxiv, ChemRxiv) appears three times (Paper Radar Pattern, Multi-Source Paper Exploration Mesh, Active Research Workflow), intake/lifecycle governance rules are duplicated between the ~50-line Boundary section and the Intake Workflow, and 请你读/精读 routing is stated four times (mode table, directive convention, step 0, detail-preservation preamble). This matches 'several unnecessary explanations or padded sections' rather than the mostly-efficient anchor 3.

2 / 5

Actionability

There is genuinely concrete guidance — the copy-paste script invocation with flags, the numbered arXiv URL resolution order with exact URL patterns, the per-platform reader mapping (微信公众号 -> wechat-article-reader), and the closed disposition enum (top_window, ranked_backlog, no_change). However, the core managed-intake steps defer to files not in the bundle ('.local/material-lifecycle/README.md', 'note-system/materials/material_wave_ranking.py'), leaving key executable details missing, which fits anchor 3 rather than 4.

3 / 5

Workflow Clarity

Multi-step processes are clearly sequenced (Intake steps 0-6, Active Research 1-7, arXiv resolution 1-6) with explicit validation gates ('Verify an intake adds exactly one record... then create the separate... ranking revision'; 'Verify the disposition... authority readback... before reporting completion') and a dedicated Self-Verification checklist including a user-highlighted point audit. It falls short of 5 because the complete intake flow must be assembled from three interleaved sections (Boundary, Intake Workflow, Self-Verification) rather than one coherent sequence, and error-recovery loops are implicit outside the Unread/PDF-fallback paths.

4 / 5

Progressive Disclosure

Against the actual bundle, the two references (references/paper-reading-protocol.md, references/decision-driven-scouting.md) are real, well-signaled markdown links, and are one level deep (no further .md references inside them); the script is real and linked with a usage example. But the 361-line body inlines ~130 lines of paper-search machinery (arXiv route, Paper Radar Pattern, Multi-Source Paper Exploration Mesh) that clearly belongs in a bundled reference file, so 'content that should be separate is inline' holds more strongly than the 'minor organization gaps' of anchor 4.

3 / 5

Total

12

/

20

Passed

Description

75%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.

A strong description that anchors concrete actions to the exact directive phrases a user would type, giving it clear what/when guidance and high distinctiveness. Its main weakness is incomplete trigger and capability coverage relative to the body: the 调研 / 整理笔记 / 继续调研 modes are never mentioned.

Suggestions

Add the missing mode triggers to the description, e.g. extend to 'process "素材:" intakes, "调研" research, and "整理笔记" note integration'.

Trim or recast the trailing sentence ('Explicit reading follows the source's argument...') as trigger-adjacent guidance, since it consumes description budget without adding a trigger or capability.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Research and triage learning materials', 'read and explain sources', 'process "素材:" intakes and "读完" closure' — matching the anchor for several specific actions with minor gaps. It falls short of 5 because body-covered capabilities like 整理笔记 note integration and 调研 active research are absent, and the trailing sentence about argument-following is boundary clarification rather than a capability.

4 / 5

Completeness

Both 'what' (research, triage, read/explain, intake, closure) and 'when' (the quoted directive phrases) are explicitly present, satisfying the equivalent-trigger-guidance requirement. 'When' falls short of the 5 anchor because trigger guidance covers only the reading/intake modes, not the research and note-integration modes the body defines.

4 / 5

Trigger Term Quality

The quoted directives "请你读" / "精读", "素材:", and "读完" are the exact phrases a user of this workflow would type, giving strong natural trigger coverage. It is not 5 because the skill's other declared triggers — "调研", "整理笔记", "继续调研" — are missing.

4 / 5

Distinctiveness Conflict Risk

The quoted command phrases (素材:, 请你读, 读完) form a clear niche with minimal collision risk against generic skills. The broad opening clause 'Research and triage learning materials' leaves minor overlap risk with general research skills, keeping it below 5.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

huangruiteng/CS-Notes

Path

.codex/skills/research-material-scout/SKILL.md

Reviewed

Table of Contents

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.