CtrlK
BlogDocsLog inGet started
Tessl Logo

oma-academic-writing

Draft and revise academic prose against a rubric, evidence, and citation requirements. Use for essays, reports, literature reviews, or academic style audits.

66

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/oma-academic-writing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 well-sequenced, actionable instruction set with strong workflow clarity and validation feedback loops. Its main weaknesses are cross-sectional redundancy that hurts conciseness, a lack of worked examples, and a progressive-disclosure chain that points to resource files which are not actually present in the bundle.

Suggestions

Deduplicate the workflow: the 6-step flow is restated in Entry, Scenes, the Actions table, and the Canonical workflow path — keep one canonical sequence and have other sections reference it to reduce token cost.

Add at least one worked example per mode (e.g., a short before/after revised paragraph and a filled 3-row Claim-Evidence Map) so the guidance is copy-paste ready for common cases.

Ship the referenced resource files (resources/anti-ai-checklist.md, sentence-structure-reference.md, academic-verb-tiers.md, hedging-guide.md) or inline the essential rules they hold, so the progressive-disclosure navigation actually resolves.

DimensionReasoningScore

Conciseness

Mostly efficient and free of basic-concept padding, but the same 6-step workflow is restated across Entry, Scenes, the Actions table, and the Canonical workflow path, and Guardrail #11 includes a long definitional paragraph on "mannered prose", matching the 3-anchor (mostly efficient but could be tightened). Not 4 because the cross-sectional redundancy is more than minor; not 2 because it is not dominated by unnecessary explanation.

3 / 5

Actionability

Concrete, executable guidance throughout (explicit sentence-length targets 8-15/16-25/26-40, em-dash/semicolon limits, banned-vocabulary rules, Topic-Support-Conclude template, Claim-Evidence Map table format, failure/recovery rows), matching the 4-anchor (mostly executable guidance with minor gaps). Not 5 because there are no worked examples (e.g., a sample revised paragraph or a filled Claim-Evidence Map) covering common cases.

4 / 5

Workflow Clarity

Clear sequence (Entry -> PREPARE/ACQUIRE/ACT/VERIFY/FINALIZE -> Exit) with explicit validation checkpoints (VERIFY audits against anti-ai-checklist, reverse outline, re-run audit) and feedback loops (failure/recovery table, restructure-two-sentences rule), matching the 5-anchor (clear sequence + explicit validation + feedback loops + checklists).

5 / 5

Progressive Disclosure

The SKILL.md is well-structured as an overview and references are clearly signaled and one-level-deep in intent (resources/anti-ai-checklist.md, sentence-structure-reference.md, academic-verb-tiers.md, hedging-guide.md, ../_shared/core/*.md), but none of these referenced files exist in the bundle, breaking the disclosure chain so a user cannot actually navigate to the detail. This matches the 3-anchor (some structure, references present, but organization undermined). Not 4 because the missing files are a real navigation defect; not 2 because the in-file structure is sound and references are not buried.

3 / 5

Total

15

/

20

Passed

Description

87%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 strong: it concisely states what the skill does and when to use it with natural trigger terms and a clear academic-writing niche. Minor gaps in action enumeration and trigger synonyms keep specificity and trigger_term_quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Draft and revise academic prose", "against a rubric, evidence, and citation requirements", "academic style audits") with a named domain, matching the 4-anchor (several specific actions, minor gaps). Not 5 because the actions cluster around draft/revise/audit with rubric/evidence/citation as modifiers rather than distinct enumerated actions; not 3 because coverage clearly exceeds 1-2 actions.

4 / 5

Completeness

Explicitly answers both what ("Draft and revise academic prose against a rubric, evidence, and citation requirements") and when ("Use for essays, reports, literature reviews, or academic style audits") with concrete trigger phrases, matching the 5-anchor exactly.

5 / 5

Trigger Term Quality

Includes natural user phrases ("essays, reports, literature reviews", "academic style audits") that a user would plausibly say, matching the 4-anchor (good keyword coverage, a few natural terms missing). Not 5 because common synonyms like "thesis", "dissertation", "academic English", or "polish my writing" are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (academic prose bound by rubric/evidence/citation) with distinct triggers (essays, reports, literature reviews, academic style audits) and minimal conflict risk, matching the 5-anchor. The academic + rubric + citation framing distinguishes it from generic writing skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
first-fluke/oh-my-agent
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.