Content
67%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, actionable planning skill with a clear ordered workflow and validation checkpoint, undermined by notable duplication between the step sections and the Hard Rules list and by three orphaned reference files that the body never links to.
Suggestions
De-duplicate the Hard Rules section: keep the step sections as the source of truth and reduce Hard Rules to only the cross-cutting constraints not already stated inline (e.g., the DESeq2/limma data-type rule and the stop-and-redirect rule).
Link the three orphaned reference files (analysis-modules.md, method-library.md, workflow-step-template.md) from the relevant steps — e.g., Step 6 for analysis modules, Step 4/Step 7-D for the workflow-step template — or remove them from the bundle if unused.
Add an explicit fix-and-retry loop to Step 5 (dependency check → fix declared dependencies → re-check before output) instead of only a one-directional downgrade, to reach the top workflow-clarity anchor.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and domain-specific, but the 23-item 'Hard Rules' section substantially restates content already in the step sections (reference rules repeated across Step 4.5, Step 7-I, and Rules 11–13/21; dependency rules across Step 5 and Rules 16–18/20), so it could be tightened. | 3 / 5 |
Actionability | Highly actionable for an instruction-only skill: exact input format, named pattern/config tables, mandatory A–J output sections with explicit required elements, verbatim redirect and Dataset Disclaimer text, and logic-formula examples; minor gaps because the concrete research content depends on user input. | 4 / 5 |
Workflow Clarity | Seven ordered steps with a mandatory Step 5 dependency-consistency check (an explicit checklist) and a feedback directive ('If dependency fails, remove or downgrade the downstream claim'); the recovery is one-directional downgrade rather than a fix-and-retry loop, keeping it just below the top anchor. | 4 / 5 |
Progressive Disclosure | Five reference files are well-signaled one-level-deep (study-patterns, workload-configurations, literature-retrieval-and-citation, figure-deliverable-plan, validation-evidence-hierarchy), but three bundle files (analysis-modules, method-library, workflow-step-template) are never referenced from the body, leaving them orphaned and unnavigable. | 4 / 5 |
Total | 15 / 20 Passed |