resubmission-deadline-tracker

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

3,891 stars

Best use case

resubmission-deadline-tracker is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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

Teams using resubmission-deadline-tracker should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/resubmission-deadline-tracker/SKILL.md --create-dirs "https://raw.githubusercontent.com/openclaw/skills/main/skills/aipoch-ai/resubmission-deadline-tracker/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/resubmission-deadline-tracker/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How resubmission-deadline-tracker Compares

Feature / Agentresubmission-deadline-trackerStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Resubmission Deadline Tracker

Track manuscript resubmission deadlines and generate actionable task schedules based on remaining time.

## Quick Check

```bash
python -m py_compile scripts/main.py
python scripts/main.py --help
```

## When to Use

- Use this skill when tracking one or more manuscript resubmission deadlines and generating a task breakdown.
- Use this skill when assessing urgency level and creating a phase-appropriate revision schedule.
- Do not use this skill to sync with journal submission systems, send automated reminders, or manage grant deadlines.

## Workflow

1. Confirm the manuscript title, journal, deadline date, and reviewer issue counts.
2. **Timezone validation:** If `--timezone` is not provided, default to `Asia/Shanghai` and emit a note: "Deadline calculated using Asia/Shanghai timezone. Use `--timezone` to specify your local timezone (e.g., `America/New_York`, `Europe/London`)."
3. Calculate remaining time and assign urgency level (standard / urgent / emergency).
4. Generate a phase-appropriate task schedule based on the urgency level.
5. Return the deadline summary, task breakdown, and risk notes.
6. If inputs are incomplete, state exactly which fields are missing and request only the minimum additional information.

## Usage

```text
# Add new deadline
python scripts/main.py --add --title "Cancer Research Paper" \
  --journal "Nature Medicine" --deadline "2024-03-15" \
  --major-issues 2 --minor-issues 8

# List all tracked deadlines
python scripts/main.py --list

# Show details for specific paper
python scripts/main.py --show "Cancer Research Paper"

# Generate task breakdown
python scripts/main.py --tasks "Cancer Research Paper"

# Update progress
python scripts/main.py --update "Cancer Research Paper" --progress 60
```

## Parameters

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| `--deadline` | date | Yes | — | Target submission date (YYYY-MM-DD) |
| `--title` | string | No | — | Manuscript title |
| `--journal` | string | No | — | Target journal name |
| `--major-issues` | integer | No | 0 | Count of major reviewer concerns |
| `--minor-issues` | integer | No | 0 | Count of minor reviewer concerns |
| `--timezone` | string | No | Asia/Shanghai | User timezone |

## Urgency Levels

| Remaining Time | Level | Mode |
|----------------|-------|------|
| > 14 days | Standard | Full 4-phase schedule |
| 3–14 days | Urgent | Triage and P0-only execution |
| < 3 days | Emergency | Minimum viable changes + extension request |

**Note:** The 3–7 day range was previously labeled "Urgent" but the boundary is 3–14 days. Any remaining time between 3 and 14 days triggers Urgent mode.

## Output

- Deadline summary with urgency status
- Phase-by-phase task schedule
- Daily targets and checkbox list
- Risk notes (timezone, submission type, buffer time)

## Stress-Case Rules

For complex multi-constraint requests, always include these explicit blocks:

1. Assumptions
2. Deadline and Urgency Assessment
3. Task Schedule
4. Risks and Caveats
5. Next Checks

## Error Handling

- If required inputs are missing, state exactly which fields are missing and request only the minimum additional information.
- If the task goes outside the documented scope, stop instead of guessing or silently widening the assignment.
- If `scripts/main.py` fails, report the failure point, summarize what still can be completed safely, and provide a manual fallback.
- Do not fabricate deadline dates, journal policies, or task estimates.

## Input Validation

This skill accepts: a manuscript resubmission deadline with optional reviewer issue counts and journal details.

If the request does not involve manuscript resubmission deadline tracking — for example, asking to manage grant deadlines, sync with journal systems, or send automated email reminders — do not proceed with the workflow. Instead respond:
> "resubmission-deadline-tracker is designed to track manuscript resubmission deadlines and generate task schedules. Your request appears to be outside this scope. Please provide a deadline date and manuscript details, or use a more appropriate tool."

## Response Template

Use the following fixed structure for non-trivial requests:

1. Objective
2. Inputs Received
3. Assumptions
4. Workflow
5. Deliverable
6. Risks and Limits
7. Next Checks

If the request is simple, you may compress the structure, but still keep assumptions and limits explicit when they affect correctness.

Related Skills

KPI Tracker Skill

3891
from openclaw/skills

Track, analyze, and report on Key Performance Indicators for any business.

Workflow & Productivity

Budget & Expense Tracker — AI Agent Financial Command Center

3891
from openclaw/skills

Track every dollar, enforce budgets, spot spending patterns, and build wealth — all through natural conversation with your AI agent.

General Utilities

game-light-tracker

3891
from openclaw/skills

Track live NFL, NBA, NHL, or MLB games and automatically change Hue light colors based on which team is leading. Use when user wants to sync smart lights with live sports scores for visual game tracking. Supports NFL, NBA, NHL, and MLB games with customizable team colors.

General Utilities

ml-experiment-tracker

3891
from openclaw/skills

Plan reproducible ML experiment runs with explicit parameters, metrics, and artifacts. Use before model training to standardize tracking-ready experiment definitions.

Data & Research

pitch-follow-up-tracker

3891
from openclaw/skills

Track outreach pitches and draft contextual follow-up emails. Monitors a pitch tracker (Google Sheet or local markdown), checks Gmail for replies, flags stale pitches, and drafts tiered follow-ups (Day 3, Day 7, Day 14) that reference the original pitch content. Use when you need to check on pitch follow-ups, draft follow-up emails, review outreach status, find pitches without replies, or manage an outreach pipeline. Triggers on: 'check follow-ups,' 'who hasn't replied,' 'draft follow-ups,' 'outreach status,' 'pitch tracker,' 'stale pitches,' or any request to manage pitch/outreach follow-up.

github-growth-tracker

3891
from openclaw/skills

Track GitHub repo growth (stars, forks, issues, commits) with periodic digests and trend analysis. Compare your repos against a watchlist. Use when checking repo stats, monitoring growth, setting up a github digest, comparing repos, or managing a repo watchlist. Requires GITHUB_TOKEN environment variable or GitHub PAT (see Credentials).

engagement-analytics-tracker

3891
from openclaw/skills

Use this skill whenever the user needs help with behavioral analytics, engagement tracking, or data collection across any digital touchpoint. Trigger for: website behavioral analytics (scroll depth, form abandonment, session tracking, GTM setup, GA4 custom events), email engagement tracking (open/click/attribution via Klaviyo, Mailchimp, or custom platforms), social media engagement monitoring (owned and competitor), mobile app analytics (Firebase, Amplitude, Mixpanel, AppsFlyer), user-level engagement scoring, cohort analysis, conversion tracking, event schema design, data layer setup, attribution modeling, or any request like "track user behavior", "set up analytics", "measure engagement", "build an event schema", "track form abandonment", "email attribution", "app retention analysis", "what events should I track?", or "how do I measure X". Always use this skill — do not guess at tracking implementations from memory; patterns and APIs change.

ad-platform-tracker

3891
from openclaw/skills

Use this skill whenever the user needs to track, analyze, or respond to advertising platform changes across Meta (Facebook/Instagram), Google Ads, or competitor intelligence. Trigger for any of these requests: Meta algorithm updates, Andromeda implications, Google Ads policy changes, Performance Max updates, privacy/compliance tracking (GDPR, CCPA, iOS), competitor ad analysis, campaign impact assessment, ad policy audits, regulatory compliance checks, platform feature rollouts, algorithm behavior changes, creative strategy updates from platform shifts, competitor ad library scraping, or any question like "what changed on Meta/Google?", "how does X update affect my campaigns?", "is my account compliant?", "what are competitors running?". Always use this skill — do not rely on training memory for fast-changing platform details.

alumni-career-tracker

3891
from openclaw/skills

Analyze laboratory alumni career trajectories and outcomes to provide data-driven career guidance for current students and postdocs. Tracks industry vs academia distribution, identifies career pathways, and generates personalized recommendations based on degree level and research interests.

tracker-latest-run-monitor

3891
from openclaw/skills

Monitor the most recent run result of a configured OpenClaw cron job and send a compact Feishu private message with the latest execution time, status, and detail. Use when a user wants a standalone skill for latest-run monitoring, cron status notifications, daily status pings, or Feishu alerts for a tracker/scheduled job regardless of success or failure.

openclaw-deploy-tracker

3891
from openclaw/skills

记录和查询 OpenClaw 生态的部署服务。当需要新增部署、查询现有服务、更新服务状态、检查依赖关系时使用。规范记录格式,提供查询和写入的工作流。无需凭证。

beijing-signed-price-tracker

3891
from openclaw/skills

Track configured Beijing Housing Commission new-home projects from bjjs.zjw.beijing.gov.cn project-detail URLs, read project signed-unit counts, signed area, and average price, crawl building tables including “查看更多” and paginated lists, treat both “已签约” and “网上联机备案” as signed units, estimate the implied average price per m² of newly signed rooms from changes between the previous and current project summaries, cache unsold room metadata locally, persist rows into a Feishu spreadsheet as the single source of truth, and send Feishu DM notifications after each run. Use when asked to monitor one or more Beijing pre-sale projects, update a project mapping, sync newly signed rooms into a Feishu sheet, infer newly signed average price, verify duplicate insertion behavior, or notify on updates.