Files
ECC/skills/scientific-thinking-scholar-evaluation/SKILL.md
T
d29cf651c7 fix(skills): declare activation triggers in descriptions and normalize version metadata (#2618)
* fix(skills): move version into metadata and normalize to semver

29 skills declared `version` at the top level of their frontmatter. The
schema reads it from `metadata`, so tooling that follows the schema either
misses it or has to special-case the top level.

Three motion skills also declared `version: 1.0`, which is not a valid
semantic version; normalized to `1.0.0`.

No behavioral change — frontmatter metadata only.

* fix(skills): state activation triggers in skill descriptions

148 skills described what they cover but never named the situation that
should trigger them. Since the description is what Claude matches against
to decide whether to load a skill, a description without a trigger makes
activation guesswork — the skill is either missed or loaded at the wrong
time.

Added a "Use when ..." clause to each, derived from the skill's own body
(most already stated the trigger under "## When to Use" or in the opening
line; that intent is now reflected in the frontmatter where it is actually
read from).

Descriptions were only appended to; no existing wording was removed.

* fix(skills): sync activation triggers into the Codex skill mirror

10 of the skills whose descriptions changed are also mirrored under
`.agents/skills/`, where the description was previously a verbatim copy.
Left alone, the two surfaces would disagree about when the skill applies.

Only the description line is synced; the Codex copies keep their reduced
frontmatter, since that validator accepts only name, description,
metadata, license, and allowed-tools.

* fix(skills): correct three activation clauses from review

- autonomous-loops: the clause pulled new loop work into a skill that its
  own body marks as a compatibility shim retained for one release. It now
  points at the canonical continuous-agent-loop instead.
- continuous-learning: the description carried the v1 routing directive
  twice; collapsed to one.
- homelab-pihole-dns: the clause fired on any broken home DNS. Narrowed to
  tasks that actually involve Pi-hole.

* chore: retain current main lockfile

---------

Co-authored-by: Çağrı Solakoğlu <cagri.solakoglu@vtcenerji.com>
Co-authored-by: haelyra <49814733+haelyra@users.noreply.github.com>
2026-08-11 23:58:14 -04:00

4.8 KiB

name, description, metadata
name description metadata
scholar-evaluation Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback. Use when evaluating academic or scientific work — papers, proposals, methods sections, or evidence quality — against a repeatable rubric.
origin
community

Scholar Evaluation

Use this skill to evaluate academic or scientific work with a repeatable rubric.

When to Use

  • Reviewing a research paper, proposal, thesis chapter, or literature review.
  • Checking whether claims are supported by cited evidence.
  • Evaluating methodology, study design, analysis, or limitations.
  • Comparing two or more papers for quality or relevance.
  • Producing structured feedback for revision.

Evaluation Scope

Start by identifying the artifact:

  • empirical research paper
  • theoretical paper
  • technical report
  • systematic or narrative literature review
  • research proposal
  • thesis or dissertation chapter
  • conference abstract or short paper

Then choose scope:

  • comprehensive: all rubric dimensions
  • targeted: one or two dimensions, such as method or citations
  • comparative: rank multiple works against the same rubric

Rubric

Score each applicable dimension from 1 to 5:

  • 5: excellent; clear, rigorous, and publication-ready
  • 4: good; minor improvements needed
  • 3: adequate; meaningful gaps but usable
  • 2: weak; substantial revision needed
  • 1: poor; major validity or clarity problems

Use N/A for dimensions that do not apply.

1. Problem and Research Question

  • Is the problem clear and specific?
  • Is the contribution meaningful?
  • Are scope and assumptions explicit?
  • Does the question match the claimed contribution?

2. Literature and Context

  • Is relevant prior work covered?
  • Does the work synthesize rather than merely list sources?
  • Are gaps accurately identified?
  • Are recent and foundational sources balanced?

3. Methodology

  • Does the method answer the research question?
  • Are design choices justified?
  • Are variables, datasets, participants, or materials described clearly?
  • Could another researcher reproduce the work?
  • Are ethical and practical constraints acknowledged?

4. Data and Evidence

  • Are data sources credible and appropriate?
  • Is sample size or corpus coverage adequate?
  • Are inclusion, exclusion, and preprocessing decisions documented?
  • Are missing data and bias risks discussed?

5. Analysis

  • Are statistical, qualitative, or computational methods appropriate?
  • Are baselines and controls fair?
  • Are uncertainty, sensitivity, or robustness checks included when needed?
  • Are alternative explanations considered?

6. Results and Interpretation

  • Are results clearly presented?
  • Do claims stay within the evidence?
  • Are figures, tables, and metrics understandable?
  • Are negative or null results handled honestly?

7. Limitations and Threats to Validity

  • Are limitations specific rather than generic?
  • Are internal, external, construct, and conclusion-validity risks addressed?
  • Does the paper distinguish speculation from demonstrated results?

8. Writing and Structure

  • Is the argument easy to follow?
  • Are sections organized around the research question?
  • Are definitions and notation clear?
  • Is the tone precise and scholarly?

9. Citations

  • Do cited papers support the claims attached to them?
  • Are primary sources used where possible?
  • Are reviews labeled as reviews?
  • Are preprints labeled as preprints?
  • Are citation metadata and links correct?

Review Process

  1. Read the abstract, introduction, figures, and conclusion for claimed contribution.
  2. Read methods and results for evidence quality.
  3. Check the strongest claims against cited sources.
  4. Score each applicable dimension.
  5. Separate critical blockers from revision suggestions.
  6. End with concrete next edits.

Output Template

# Scholar Evaluation: <Artifact>

## Overall Assessment

- Overall score: <1-5 or N/A>
- Confidence: <high | medium | low>
- Summary: <3-5 sentences>

## Dimension Scores

| Dimension | Score | Evidence | Revision priority |
| --- | ---: | --- | --- |
| Problem and question |  |  |  |
| Literature and context |  |  |  |
| Methodology |  |  |  |
| Data and evidence |  |  |  |
| Analysis |  |  |  |
| Results and interpretation |  |  |  |
| Limitations |  |  |  |
| Writing and structure |  |  |  |
| Citations |  |  |  |

## Critical Issues

## Recommended Revisions

## Evidence Checks Needed

Pitfalls

  • Do not use the score as a substitute for concrete feedback.
  • Do not penalize a paper for omitting a dimension outside its scope.
  • Do not treat citation count, venue, or author reputation as proof of quality.
  • Do not accept unsupported claims just because they appear in the abstract.