Moved — use the scientific-method plugin instead.
62
Quality
42%
Does it follow best practices?
Impact
99%
2.91xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/scientific-thinking/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is a deprecation notice rather than a functional skill description. It provides no information about capabilities, use cases, or trigger conditions, making it completely unusable for skill selection. The description should either be removed entirely or replaced with actual content if the skill is still active.
Suggestions
If this skill is deprecated, remove it from the skill library entirely rather than leaving a redirect notice.
If the skill should remain, replace the redirect notice with a proper description that explains what the skill does (e.g., 'Applies scientific method principles to problem-solving...') and when to use it.
Add a 'Use when...' clause with natural trigger terms users would say when needing scientific method guidance (e.g., 'hypothesis', 'experiment', 'research methodology').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states the skill has been moved and redirects to another plugin, providing zero information about what the skill actually does. | 1 / 3 |
Completeness | The description answers neither 'what does this do' nor 'when should Claude use it'. It is purely a redirect notice with no functional information. | 1 / 3 |
Trigger Term Quality | The only keyword present is 'scientific-method' which is a reference to another plugin, not a natural trigger term a user would say. No domain-relevant keywords are included. | 1 / 3 |
Distinctiveness Conflict Risk | The description provides no distinguishing characteristics. It cannot be differentiated from any other skill since it describes no capabilities or use cases. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured redirect notice that efficiently communicates the skill has moved. It provides the essential information (new path, invocation command) without unnecessary explanation. However, as a redirect rather than actual skill content, it doesn't demonstrate the qualities of a substantive skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is maximally concise - it communicates exactly what's needed (the skill moved, where it went, how to invoke it) with zero unnecessary explanation. | 3 / 3 |
Actionability | Provides the new location and invocation command, which is actionable for finding the skill, but offers no actual skill content or guidance since it's just a redirect notice. | 2 / 3 |
Workflow Clarity | For a redirect/deprecation notice, the single action (go to new location) is completely unambiguous with a direct link and invocation syntax. | 3 / 3 |
Progressive Disclosure | Appropriately structured as a minimal redirect with a clear one-level-deep reference to the actual skill location. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
5667e97
Table of Contents
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.