Content
63%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 thorough, well-structured drug-safety workflow with highly actionable tool specifics and a clear phase sequence. It is somewhat verbose and monolithic — trimming redundant prose and splitting the tool/interpretation reference into bundle files would improve token efficiency and navigation.
Suggestions
Remove the opening paragraph that duplicates the frontmatter description and tighten the 'Guiding principles' list to avoid restating points already made in later sections.
Extract the per-phase tool reference (input/output schemas) and the FAERS signal-interpretation table into a reference file under ./references/, keeping SKILL.md as a workflow overview that links one level deep.
Show at least one literal, copy-paste-ready tool invocation example (e.g., a FAERS disproportionality call with real arguments) to bridge the gap between described and executable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly dense and tool-focused, but the opening paragraph duplicates the description, the 'Guiding principles' section restates earlier points, and some conceptual prose (ICD-10 vs SNOMED flavor) could be trimmed without losing actionability. | 3 / 5 |
Actionability | Concrete tool names with exact input/output parameters (e.g., 'setid NOT set_id', 'medicinalproduct NOT drug_name'), explicit signal thresholds (PRR >= 2.0, lower CI > 1, N >= 3), and query tips give mostly executable guidance, though tool calls are described rather than shown as literal invokable syntax. | 4 / 5 |
Workflow Clarity | A clear 7-phase (0-6) sequence with per-phase numbered workflows and a 5-step signal-credibility validation checklist; minor gaps in explicit validate-then-proceed feedback loops, but operations are read-only so no destructive-cap applies. | 4 / 5 |
Progressive Disclosure | Well-organized into clear sections, but the skill is a single monolithic ~14KB file with no bundle files; content such as the full per-tool reference and FAERS interpretation tables is inlined that could plausibly live in separate reference files. | 3 / 5 |
Total | 14 / 20 Passed |