meta-research-to-slide-deck

Use this meta-skill instead of answering directly when the user needs a researched presentation, leadership briefing, competitive analysis deck, or source-backed slide outline that benefits from multi-skill orchestration across search, source curation, synthesis, slides, and document export.

Quality

58%

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

Fix and improve this skill with Tessl

tessl review fix ./src/opensquilla/skills/exp/meta-research-to-slide-deck/SKILL.md

Quality

Content

33%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 extremely lean but provides almost no usable guidance: it restates the description without steps, references, or structure. The real workflow is buried in frontmatter composition rather than surfaced for the reader.

Suggestions

Add a short workflow overview in the body that mirrors the composition steps (brief → clarify → search → research → storyline → pptx → final brief) so the sequence and validation checkpoints are visible.

Reference the orchestrated skills (multi-search-engine, deep-research, pptx) and any expected inputs/outputs at each step so the body is actionable rather than purely descriptive.

Include a brief "what to verify before presenting" checkpoint to satisfy the validation expectation for a multi-step, batch-style generation workflow.

Dimension	Reasoning	Score
Conciseness	The body is a single H1 and one sentence with zero padding or restated concepts; it assumes Claude's competence and wastes no tokens.	5 / 5
Actionability	"Builds source-backed presentation packages from a research question" only describes the outcome; it gives no concrete steps, commands, or executable guidance.	1 / 5
Workflow Clarity	The body contains no sequenced steps or validation checkpoints; the actual multi-step workflow lives only in the YAML frontmatter, which is out of scope for this rubric.	1 / 5
Progressive Disclosure	Beyond the H1 there is no structure, no sections, and no signaling to the orchestrated skills (multi-search-engine, deep-research, pptx) or any bundle files; navigation is effectively absent.	2 / 5
	Total	9 / 20 Passed

Description

83%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, well-structured description that clearly states capabilities and explicit use-conditions with natural trigger phrases. Minor improvements would come from adding common synonyms (research deck, PPT) to broaden trigger coverage.

Suggestions

Add high-frequency synonyms such as "research deck" and "PPT" (and bilingual terms like "汇报材料" / "竞品分析PPT") to the description to match the frontmatter triggers and broaden natural-term coverage.

Tighten the capability list from the abstract "multi-skill orchestration across ..." framing to concrete verbs (e.g., "searches, curates sources, synthesizes findings, builds slides, exports decks") to lift specificity toward 5.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete capabilities via "multi-skill orchestration across search, source curation, synthesis, slides, and document export," though the orchestration framing is slightly more abstract than crisp action verbs.	4 / 5
Completeness	It explicitly answers both what (source-backed researched presentations via multi-skill orchestration) and when ("Use this meta-skill ... when the user needs ...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	It includes natural phrases users would say ("researched presentation," "leadership briefing," "competitive analysis deck," "source-backed slide outline") but omits common synonyms like "research deck," "PPT," or the bilingual triggers listed in frontmatter.	4 / 5
Distinctiveness Conflict Risk	The researched-deck meta-skill niche is clear and distinct, with only minor overlap risk against the underlying research, search, and pptx skills it orchestrates.	4 / 5
	Total	17 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: TokenRhythm/opensquilla
Path: src/opensquilla/skills/exp/meta-research-to-slide-deck/SKILL.md
Commit: 94ac35e

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