seed

Add a source file to the processing queue. Checks for duplicates, creates archive folder, moves source from inbox, creates extract task, and updates queue. Triggers on "/seed", "/seed [file]", "queue this for processing".

Quality

92%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is highly actionable and clearly sequenced with strong validation gates for a batch file-mutating operation. Its only weakness is conciseness: several rationale/explanation sections add prose beyond the executable workflow.

Suggestions

Trim the "Why This Skill Exists", "Why move immediately", and "Naming Convention" sections to one line each or fold them into the relevant steps, since the executable bash already conveys the behavior.

Consider moving the large YAML/JSON/markdown task-file templates in Steps 6–7 into a references file to reduce the SKILL.md body length, which would also strengthen progressive disclosure.

Collapse the "Source Handling Patterns" ASCII diagrams into the Step 4 narrative to avoid restating the inbox-vs-living-doc distinction a second time.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with dense, executable bash and templates assuming Claude's competence, but the "Why This Skill Exists", "Why move immediately", and "Naming Convention" prose sections add explanatory material beyond what is needed to execute; per the rubric verbosity is penalized even when accurate, so it sits at the score-2 anchor of mostly efficient but with some unnecessary explanation.	2 / 3
Actionability	Provides fully executable bash (duplicate-detection grep/find, mkdir, mv, claim-number arithmetic) and complete copy-paste-ready task-file templates in markdown, YAML, and JSON, matching the score-3 anchor rather than the score-2 pseudocode anchor.	3 / 3
Workflow Clarity	Eight explicitly numbered steps with validation checkpoints (source-existence error block, duplicate "Proceed anyway? (y/n)" gate, global claim-uniqueness check) and error-recovery handling match the score-3 anchor; the always/never Critical Constraints list acts as a checklist, and validation is present rather than missing for this batch/destructive operation.	3 / 3
Progressive Disclosure	No bundle files exist, so organization is judged on the single-file body; sections are clearly headed and one level deep with no nested external reference chains, matching the score-3 spirit of clear organization and easy navigation given there is no content that should be split out.	3 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinct: it lists concrete actions, gives explicit invocation triggers, and occupies a clear niche. Voice is correctly third person with no first/second-person phrasing, so no specificity penalty applies.

Dimension	Reasoning	Score
Specificity	Enumerates five concrete actions ("Checks for duplicates, creates archive folder, moves source from inbox, creates extract task, and updates queue"), matching the score-3 anchor of listing multiple specific concrete actions rather than naming only the domain plus a few actions.	3 / 3
Completeness	Explicitly answers both "what" (the five-action queue-seeding workflow) and "when" via an explicit "Triggers on ..." clause, satisfying the score-3 anchor that requires both with explicit triggers; it is not score 2 because the trigger guidance is stated directly rather than merely implied.	3 / 3
Trigger Term Quality	Provides natural trigger terms a user would actually say ("/seed", "/seed [file]", "queue this for processing"); these are not jargon and give good coverage of the terms a user would use to invoke this skill.	3 / 3
Distinctiveness Conflict Risk	The slash-command triggers and narrow "seed a source into the processing queue" niche make it clearly distinct and unlikely to fire for an unrelated skill, matching the score-3 anchor of a clear niche with distinct triggers.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: agenticnotetaking/arscontexta
Path: skill-sources/seed/SKILL.md
Commit: 2acfd5c

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