CtrlK
BlogDocsLog inGet started
Tessl Logo

wiki-research

Autonomously research a topic via multi-round web search, synthesize findings, and file structured results into the Obsidian wiki. Use this skill when the user says "/wiki-research [topic]", "research X", "find everything about Y", "do a deep dive on Z", "autonomous research on X", or wants comprehensive, web-sourced knowledge on a topic filed directly into their wiki.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 well-structured, actionable research workflow with strong sequencing, a halt condition, a checklist, and error-recovery loops. The main weakness is verbosity from duplicated YAML examples and sections that restate earlier steps.

Suggestions

Remove the duplicate backends YAML: keep only one of the inline example (lines 43-60) or the starter registry template (lines 81-110), referencing the other rather than reproducing it.

Collapse the 'Research Configuration' and 'Research Backends' sections into the corresponding 'Before You Start' steps (4 and 5) to avoid restating the same vault-file checks twice.

Add an explicit pre-filing validation checkpoint (e.g., 'verify all source/concept/entity pages render and required frontmatter fields are set before updating index.md') to strengthen the batch-write workflow.

DimensionReasoningScore

Conciseness

Mostly efficient operational detail with no 'what is a PDF'-style filler, but it carries noticeable redundancy — the backends YAML is shown twice (lines 43-60 and 81-110) and the Research Configuration/Backends sections repeat steps already in 'Before You Start'.

3 / 5

Actionability

Provides concrete, mostly copy-paste-ready guidance — executable qmd/bash commands, exact frontmatter templates with named fields, log.md and .manifest.json format strings — with only minor gaps where synthesis is left abstract.

4 / 5

Workflow Clarity

Clear sequence (config → Round 1/2/3 → Filing → Cross-linking → Tracking → QMD) with a halt condition, a Quality Checklist, and error-recovery feedback loops (backend failure falls back to WebSearch; QMD failure does not roll back vault). Minor gap: no inline pre-file validation checkpoint before writing pages.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections and delegates config/writing-profile detail to the canonical llm-wiki/SKILL.md (one-level-deep, clearly signaled). No bundle files exist to split further; minor organization gaps come from the long inline backends YAML that could live in a reference file.

4 / 5

Total

15

/

20

Passed

Description

96%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 strong, concrete description that clearly states capabilities and provides rich, natural trigger phrases. Its only weakness is that several natural-language triggers are generic enough to overlap with general research skills, slightly raising conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'research a topic via multi-round web search, synthesize findings, and file structured results into the Obsidian wiki' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (research, synthesize, file into Obsidian wiki) and 'when' ('Use this skill when the user says...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes a broad set of natural phrases users would say — '/wiki-research [topic]', 'research X', 'find everything about Y', 'do a deep dive on Z', 'autonomous research on X' — with synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

The '/wiki-research' slash command and Obsidian-wiki-filing niche make it mostly distinct, but generic triggers like 'research X' and 'do a deep dive on Z' carry minor overlap risk with other research skills.

4 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
Ar9av/obsidian-wiki
Reviewed

Table of Contents

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.