resubmission-deadline-tracker

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

Quality

65%

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

Quality

Content

73%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 content is highly actionable with executable examples and a clear sequenced workflow, but it is undermined by orphaned bundle files that are never referenced from the body, hurting progressive disclosure.

Suggestions

Add explicit, one-level-deep references to the existing bundle files (e.g., under an 'Advanced' or 'References' section: 'Reviewer-issue checklists: see references/revision_checklist.md', 'Journal deadline data: see references/journal_deadlines.md', 'Task templates: see references/task_templates.json') so they are discoverable rather than orphaned.

Tighten or consolidate the Stress-Case Rules and Response Template sections, which overlap with the Workflow and Output sections, to reduce redundancy.

Make the validation feedback loop explicit (e.g., 'If --add fails validation, fix the flagged field and re-run --add') to lift workflow_clarity toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with well-organized tables and code blocks, but the Stress-Case Rules and Response Template sections partially restate information already covered elsewhere and could be trimmed.	4 / 5
Actionability	Executable copy-paste-ready commands are given for every common case (add, list, show, tasks, update) with full flag examples, a parameter table, and concrete output descriptions covering the main cases.	5 / 5
Workflow Clarity	The Workflow section is clearly numbered and includes validation steps (timezone validation, input validation, scope checks), but a couple of checkpoints are implicit and the destructive/batch validation feedback loop (validate -> fix -> retry) is only weakly present via the Error Handling fallback note.	4 / 5
Progressive Disclosure	Bundle files exist in references/ (journal_deadlines.md, revision_checklist.md, task_templates.json) and scripts/ (main.py) but the body never references or signals them, leaving them orphaned; inlining that belongs in separate files plus unsignaled references matches the 'minimal structure / references buried' anchor.	2 / 5
	Total	15 / 20 Passed

Description

56%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 specific and distinct but omits an explicit 'Use when...' trigger clause, capping its completeness, and lacks broader natural phrasing/synonyms that users would actually say.

Suggestions

Add an explicit 'Use when...' trigger clause naming concrete situations (e.g., 'Use when revising and resubmitting a manuscript, tracking a revise-and-resubmit deadline, or planning a revision schedule').

Include natural user phrasings and synonyms such as 'paper revision', 'reviewer response deadline', and 'revise and resubmit' to improve trigger-term coverage.

Consider adding one or two more concrete actions (e.g., 'assign urgency level', 'schedule revision phases') to round out the capability list toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ('Track manuscript resubmission deadlines and automatically generate phase-appropriate task breakdowns ... based on remaining time') but 'generate task breakdowns' is somewhat generic with minor gaps in coverage.	4 / 5
Completeness	It has a clear 'what' (track deadlines, generate task breakdowns) but no explicit 'Use when...' trigger clause or equivalent 'when' guidance; the judging guideline caps completeness at 3 when such a clause is absent.	3 / 5
Trigger Term Quality	Relevant keywords are present ('manuscript resubmission deadlines', 'task breakdowns', 'remaining time') but common natural user phrasings and synonyms (e.g., 'paper revision', 'reviewer response deadline', 'revise and resubmit') are missing.	3 / 5
Distinctiveness Conflict Risk	The niche is fairly distinct ('manuscript resubmission deadlines ... phase-appropriate task breakdowns for academic researchers') with only minor overlap risk against generic deadline or task-tracking skills.	4 / 5
	Total	14 / 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
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
Commit: 63c61d3

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