autoresearch

Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find everything about, research and file, go research, build a wiki on.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

The body is a tightly written, executable research-loop contract with clear sequencing, explicit validation gates, and well-signaled references to detailed contracts. It avoids explaining concepts Claude already knows and keeps detailed material one reference deep.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: no padding explaining what research or vaults are, and each line carries an instruction or a constraint that earns its place.	5 / 5
Actionability	Provides concrete, copy-paste-ready commands ("python3 \"$CORE\" transaction inspect …", "transaction apply … --approved-plan-sha256 …") plus specific ledger states, file paths, and budget numbers covering the common cases.	5 / 5
Workflow Clarity	Sequences the process explicitly — contract, loop, assess evidence, file dossier, separate merge — with validation checkpoints (inspect before apply, approval SHA gate, "transaction recover" after interruption) appropriate for the destructive vault-write operations.	5 / 5
Progressive Disclosure	Acts as an overview with well-signaled one-level-deep references (references/program.md is a real bundle file; ../wiki/references/provenance.md and operation-transactions.md are vault-side contracts), keeping the body a navigable map rather than a monolith.	5 / 5
	Total	20 / 20 Passed

Description

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

The description is concise yet comprehensive: it names concrete capabilities, gives an explicit Use-when clause, and supplies a rich set of natural trigger terms. It is third-person and free of vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "run a bounded, source-grounded research loop," "draft a cited dossier," and "optionually propose a separately reviewed canonical vault merge" — matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly answers both what (research loop, dossier, merge proposal) and when ("Use when the user wants autonomous or deep research that may access the public web") with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Provides broad natural phrases a user would actually say — "research this topic," "deep dive into," "investigate," "find everything about," "go research" — plus the /autoresearch slash command, giving comprehensive synonym coverage.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — bounded source-grounded web research coupled to a vault merge proposal — with distinct triggers, giving minimal overlap risk with other skills.	5 / 5
	Total	20 / 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
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: AgriciDaniel/claude-obsidian
Path: skills/autoresearch/SKILL.md
Commit: ad67087

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