results-report

This skill should be used when the user asks to "write an experiment report", "summarize experimental results", "do experiment retrospection", "write a results report", "写实验总结报告", "写实验复盘", or mentions turning completed experiment artifacts into a structured, decision-oriented research report. It assumes strict analysis should come from `results-analysis` first.

Quality

91%

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

Quality

Content

88%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 a well-structured, decision-oriented instruction skill with concrete templates, an explicit validation hard gate, and clearly signaled references. It loses a little on conciseness due to naming/frontmatter duplication and on progressive disclosure due to a referenced example file that is absent from the bundle.

Suggestions

Add the missing examples/example-results-report.md file referenced in the Reference files section, or remove that reference from the body to avoid a broken link.

De-duplicate the report naming contract and frontmatter fields between the body and references/report-naming.md by keeping only a brief summary in the body and pointing to the reference for the full spec.

Consider trimming the repeated enumeration of required analysis bundle artifacts (they appear in both the hard gate and Workflow step 2) to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no padding or explanation of concepts Claude already knows, but the naming contract and frontmatter appear in both the body and references/report-naming.md, a minor redundancy that could be tightened.	4 / 5
Actionability	Concrete and specific for an instruction-only skill: filename templates, a full frontmatter example, a fixed 10-section structure, and a hard gate specifying exactly which bundle artifacts must exist before proceeding.	5 / 5
Workflow Clarity	A clearly sequenced 6-step workflow with explicit validation (the hard gate checks for missing analysis-report.md/stats-appendix.md/figure-catalog.md and routes back to results-analysis rather than proceeding), plus a feedback loop for missing bundles.	5 / 5
Progressive Disclosure	Good structure with one-level-deep, well-signaled references that map to real files, but the body references 'examples/example-results-report.md' which does not exist in the bundle, a broken reference that slightly degrades navigation.	4 / 5
	Total	18 / 20 Passed

Description

95%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 strong: it explicitly states what the skill does and when to use it, with a rich set of natural bilingual trigger phrases and clear boundary statements against related skills. The only minor gap is that capabilities are conveyed through triggers rather than a list of distinct concrete actions.

Dimension	Reasoning	Score
Specificity	It names the domain and a concrete action ('turning completed experiment artifacts into a structured, decision-oriented research report'), but capability coverage is expressed mostly through trigger phrases rather than a list of distinct concrete actions, leaving minor gaps.	4 / 5
Completeness	It explicitly answers 'what' (structured, decision-oriented research report) and 'when' with a clear 'This skill should be used when the user asks to...' clause listing concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases in both English and Chinese ('write an experiment report', 'summarize experimental results', '写实验总结报告', '写实验复盘') including synonyms and the 'results report' variation.	5 / 5
Distinctiveness Conflict Risk	Clear niche (post-experiment reporting) with explicit boundaries against sibling skills 'results-analysis' and 'publication-chart-skill', minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Galaxy-Dawn/claude-scholar
Path: skills/results-report/SKILL.md
Commit: 6ed46da

Reviewed: 8 days 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.