emu-bulk-upload

Help museum insect curators bulk upload specimen data to the Emu database. Maps any input format to Emu's template, matches localities to existing records, finds parent sites, creates bulk upload tables, and walks users through the upload process.

Quality

82%

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

82%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.

A highly actionable, well-sequenced workflow with excellent executable commands and good progressive disclosure via real bundle files. The main gaps are minor: some trimmable example prose, no explicit script-output verification step, an orphaned reference file, and stub planned phases.

Suggestions

Add an explicit validation checkpoint after each script run (e.g. assert row counts or schema of /tmp/emu_user_sites.json before proceeding) to close the workflow_clarity gap.

Surface references/political_ranks.md from the body (e.g. in the Key reference files list or Step 1.5) so it is navigable rather than orphaned.

Tighten the longer example dialogues and the column-mapping illustration to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no concept-explanation padding Claude already knows, though several illustrative example dialogues and the mapping table could be trimmed; sits above the 3 anchor but not perfectly lean.	4 / 5
Actionability	Fully executable guidance throughout — exact commands ('python3 scripts/parse_user_data.py /tmp/emu_user_data.xlsx /tmp/emu_user_sites.json'), file paths, hex color codes (FFCCFFCC), CLI flags, and the irn_mapping.json format are copy-paste ready.	5 / 5
Workflow Clarity	Clear multi-phase sequence (Session start → Step 1 → Phase 1.1–1.8) with confirmation gates, score-threshold match review, and confidence-based rank handling; minor validation gaps (no explicit script-output verification) and Phases 2–4 are planned stubs keep it below 5.	4 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled one-level-deep references (§ pointers into phase1_sites.md, per-script references); minor gaps are the orphaned political_ranks.md not surfaced from the body and forward-references to not-yet-created phase2/phase3 files.	4 / 5
	Total	17 / 20 Passed

Description

75%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.

A specific, well-scoped description with concrete actions and a clear niche, but it omits an explicit 'Use when…' trigger clause, which caps its completeness. Adding a trigger sentence would lift it to the top band.

Suggestions

Append an explicit trigger clause, e.g. 'Use when a curator needs to bulk upload insect specimen data to Emu, match localities to existing site records, or prepare tabular data for Emu upload.'

Add common synonyms and file extensions (e.g. '.xlsx', 'spreadsheet', 'CSV') to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Maps any input format to Emu's template', 'matches localities to existing records', 'finds parent sites', 'creates bulk upload tables', 'walks users through the upload process' — covering the workflow comprehensively.	5 / 5
Completeness	The 'what' is clear and detailed, but the frontmatter description has no explicit 'Use when…' trigger clause; per the guideline a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a curator would say ('bulk upload', 'Emu', 'specimen data', 'localities', 'sites') but omits synonyms and file extensions like .xlsx, so it falls short of the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The niche is sharply defined — 'museum insect curators', 'Emu database', specimen/locality/site work — giving it distinct triggers with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: brunoasm/my_claude_skills
Path: Emu_bulk_upload_FMNH/SKILL.md
Commit: 5bdff99

Reviewed: 6 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.