CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

resubmission-deadline-tracker

Track manuscript resubmission deadlines and automatically generate phase-appropriate task breakdowns for academic researchers based on remaining time.

Quality

69%

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 ./scientific-skills/Other/resubmission-deadline-tracker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 largely executable and well-structured with genuine validation checkpoints, but it is held back by redundant scope/refusal restatements across three sections, a broken requirements.txt reference, and bundle reference files that are never linked from the SKILL.md. Linking the references and de-duplicating the scope language would raise most dimensions.

Suggestions

Link the bundle files explicitly (e.g., 'Journal policies: see [references/journal_deadlines.md](references/journal_deadlines.md)', 'Task templates: see references/task_templates.json') so the progressive-disclosure layer is discoverable.

Remove the duplicated scope statement: keep the refusal message in one place ('Input Validation') and drop the repeated sentence in 'Error Handling' and the overlapping 'Stress-Case Rules'/'Response Template' pair.

Fix the dependency note: either ship requirements.txt or replace 'pip install -r requirements.txt' with the actual install command (e.g., 'pip install tzdata' for Windows zoneinfo data).

DimensionReasoningScore

Conciseness

The tables and CLI examples are tight, but the body states its scope three times ('When to Use', 'Input Validation' with a full refusal message, and again in 'Error Handling'), repeats the sentence 'state exactly which fields are missing and request only the minimum additional information' verbatim (Workflow step 6 and Error Handling), and carries overlapping 'Stress-Case Rules' and 'Response Template' sections plus the odd meta-line 'These levels describe the existing implementation; no new states are introduced.' This is 'mostly efficient but ... could be tightened', not a 4, since the duplication spans multiple sections rather than being minor.

3 / 5

Actionability

Copy-paste-ready CLI examples cover the common cases (add, list, show, tasks, update), all documented flags exist in scripts/main.py, and the parameter/urgency tables are concrete. Not a 5 because the Dependencies section instructs 'pip install -r requirements.txt' but no requirements.txt exists in the bundle, so that command fails as shipped; not a 3 because everything else is executable and complete rather than pseudocode.

4 / 5

Workflow Clarity

The Workflow is clearly sequenced with validation checkpoints: a Quick Check (py_compile + --help), timezone validation before saving, rejection of invalid dates/zones/DST edge cases before a record is written, and an explicit failure path ('report the failure point, summarize what still can be completed safely, and provide a manual fallback'). Not a 5 because there is no fix-and-revalidate retry loop, and input validation on incomplete inputs is stated but the exact re-entry point into the workflow is left implicit.

4 / 5

Progressive Disclosure

Section structure is well organized, but the bundle contains references/journal_deadlines.md, references/revision_checklist.md, and references/task_templates.json that are never mentioned or linked from SKILL.md, so the detailed material is undiscoverable — 'references present but not clearly signaled'. Not a 2 because the SKILL.md body itself is not an inlined monolith and the structure is more than minimal; not a 4 because the reference files are completely unsignaled rather than mostly clear.

3 / 5

Total

14

/

20

Passed

Description

61%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 clear, third-person description with a concrete 'what' and a well-defined niche, but it omits any 'when to use' trigger clause, which caps completeness and weakens trigger-term coverage. Adding an explicit 'Use when tracking a manuscript revision or resubmission deadline, responding to reviewer comments, or building a revision schedule' clause would lift both completeness and trigger quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user mentions a manuscript revision or resubmission deadline, reviewer comments, or needs a revision schedule.'

Include natural synonyms users would say — 'revision', 'reviewer response', 'rebuttal', 'paper' — alongside 'resubmission' to broaden trigger coverage.

Consider mentioning one more concrete action (e.g., urgency assessment against remaining days) so the capability list reads as several specific actions rather than two.

DimensionReasoningScore

Specificity

The description names its domain ('manuscript resubmission deadlines') and two concrete actions ('Track ... deadlines' and 'automatically generate phase-appropriate task breakdowns ... based on remaining time'), matching the '1-2 concrete actions, but not comprehensive' anchor. It is not a 4 because it does not list several specific actions (e.g., urgency assessment, schedule generation, risk notes are only implied), and not a 2 because the actions are concrete rather than generic.

3 / 5

Completeness

The 'what' is clear (track resubmission deadlines, generate phase-appropriate task breakdowns), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is entirely absent, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' half is concrete and specific, not vague.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say: 'manuscript', 'resubmission', 'deadlines', 'task breakdowns', 'academic researchers', 'remaining time'. Not a 5 because common synonyms a user would naturally use are missing ('revision', 'reviewer comments/response', 'rebuttal', 'paper'); not a 3 because coverage goes beyond bare domain naming with several natural trigger phrases.

4 / 5

Distinctiveness Conflict Risk

The niche is well qualified ('manuscript resubmission', 'academic researchers', 'phase-appropriate task breakdowns'), making it mostly distinct with minor overlap risk against generic deadline/task-tracker skills. Not a 5 because without explicit 'use when' triggers, generic deadline-tracking requests could plausibly match; not a 3 because the domain qualifiers are specific enough to avoid broad overlap.

4 / 5

Total

14

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Other/resubmission-deadline-tracker/SKILL.md

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.