resubmission-deadline-tracker
Monitor resubmission deadlines for academic papers and automatically break down tasks based on remaining time. Trigger when user mentions "resubmission deadline", "revision due", "paper deadline", "revise and resubmit deadline", "R&R deadline", or needs to track manuscript revision timelines.
75
62%
Does it follow best practices?
Impact
100%
1.01xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/Academic Writing/resubmission-deadline-tracker/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description with excellent trigger term coverage and clear distinctiveness for the academic paper revision niche. The main weakness is that the capability description could be more specific about what actions are actually performed (e.g., what does 'break down tasks' produce, how is monitoring implemented). The explicit 'Trigger when' clause with comprehensive natural language terms is a strong point.
Suggestions
Expand the capability description to specify concrete outputs, e.g., 'creates prioritized task lists', 'sends reminder notifications', or 'generates revision schedules'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (academic paper resubmissions) and two actions ('monitor resubmission deadlines' and 'break down tasks based on remaining time'), but lacks comprehensive detail on what specific actions are performed (e.g., how tasks are broken down, what monitoring entails, notification mechanisms). | 2 / 3 |
Completeness | Clearly answers both what ('Monitor resubmission deadlines...automatically break down tasks based on remaining time') and when ('Trigger when user mentions...' with explicit list of trigger phrases). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'resubmission deadline', 'revision due', 'paper deadline', 'revise and resubmit deadline', 'R&R deadline', and 'manuscript revision timelines' - these are all terms academics naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on academic paper resubmissions and R&R deadlines. The specific academic terminology ('R&R', 'manuscript revision', 'revise and resubmit') makes it highly distinguishable from generic deadline or task management skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill suffers from severe verbosity, padding the content with boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Prerequisites, Lifecycle Status) that provide no actionable guidance for Claude. The core concept - task templates based on remaining time - is useful, but the implementation details are incomplete (referenced scripts don't exist) and the document is roughly 3x longer than necessary.
Suggestions
Remove all boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Prerequisites) - these add no actionable value and waste tokens
Either provide the actual Python implementation for date calculations and task generation, or remove the CLI section and focus on the task templates as the primary output
Add validation steps: verify deadline parsing is correct, confirm timezone interpretation, check that generated schedule makes sense before presenting
Consolidate the task templates into a single concise reference table rather than repeating full checklists for each time range
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that add no value. Explains obvious concepts like 'what to use this for' and includes redundant sections. The skill could be reduced to 1/3 its size while preserving all actionable content. | 1 / 3 |
Actionability | Provides concrete task templates and CLI examples which are useful, but the Python scripts referenced don't exist or aren't shown. The command-line usage shows commands but no actual implementation. Task breakdowns are helpful checklists but lack executable code for the core date calculation logic. | 2 / 3 |
Workflow Clarity | The 4-step workflow is clearly sequenced and task templates provide good phase breakdowns. However, there are no validation checkpoints - no verification that deadline was parsed correctly, no confirmation steps before generating schedules, and no error recovery guidance if calculations seem wrong. | 2 / 3 |
Progressive Disclosure | References external files (references/task_templates.json, etc.) appropriately, but the main document is bloated with sections that should be separate or removed entirely. The core actionable content is buried among boilerplate sections like Risk Assessment and Security Checklist that don't belong in the skill body. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- aipoch/medical-research-skills
- Commit
4a48721
- 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.