← ClaudeAtlas

synclisted

Build or update the estimator's history dataset by fetching Jira tickets via the Atlassian MCP — both the initial setup and periodic top-ups (new or missing resolved tickets). Use when the user wants to set up the estimator, or (re)build / refresh / sync the estimation history from Jira.
vslipchenko/ai · ★ 0 · AI & Automation · score 68
Install: claude install-skill vslipchenko/ai
# Estimator — Sync History from Jira This skill builds and updates `<DATA_DIR>/history.csv`: the estimation baseline of resolved Jira tickets. Run it for the initial setup, and re-run it periodically to top up new or missing tickets — **refresh** (full re-fetch) or **append** (only tickets resolved since the last run). You (the model) do the interactive + Jira work; a bundled script does the CSV assembly. ## Read-only Jira access This skill treats Jira purely as a **data source**. Use only read operations — `atlassianUserInfo`, `getAccessibleAtlassianResources`, project/field metadata, `searchJiraIssuesUsingJql`, `getJiraIssue`, `getJiraIssueRemoteIssueLinks`. You MUST NOT call any operation that creates, edits, transitions, comments on, links, assigns, deletes, or logs work against Jira issues (or writes to Confluence). If a step seems to require a write, stop and tell the user instead of proceeding. ## Data location Resolve `<DATA_DIR>` once and reuse it everywhere below — the per-user data dir `~/.estimator` (a normal home dotfolder, like `~/.aws`; uninstalling the plugin does NOT remove it — use `/estimator:reset` to clear it): - Bash: `DATA_DIR="$HOME/.estimator"` - PowerShell: `$DATA_DIR = Join-Path $env:USERPROFILE '.estimator'` This is a single global directory per plugin (not per project), so the dataset is fetched once and reused from any working directory. Files in `<DATA_DIR>`: - `history.csv` — the ticket dataset (13 columns; see the build script) - `conf