Drag
Operate Tempo Cloud worklogs with Drag. Use when an agent needs to configure Drag, choose a command, inspect its contract, or follow shared automation and safety rules.From its SKILL.md
npx -y skills add treramey/drag --skill dragAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.7 KB, 594 tokens by cl100k_base, as published. Nobody here has run it
Drag CLI
Use drag to work with Tempo Cloud through stable structured output and explicit dry-run paths.
Agent workflow
- Run
drag doctorwhen configuration state is uncertain. Do not print credential values. - Prefer
drag --output json <command>for automation. NDJSON is supported only bylist. - Inspect
drag <command> --helpbefore constructing unfamiliar arguments. - Inspect the complete machine contract with
drag schema. - Preview mutations with
--dry-run; execute them only when the user's request explicitly authorizes the change.
Task skills
| Skill | Command | Description |
|---|---|---|
drag-log | drag log | Add a worklog using a duration or interval |
drag-list | drag list | List worklogs for a date without changing Jira or Tempo |
drag-delete | drag delete | Delete one or more worklogs |
Configuration and secrets
- Use interactive
drag setuponly when the user can complete terminal prompts. - For unattended setup, supply credentials through documented environment variables and use
drag setup --from-env. - Never echo, log, summarize, or include Atlassian or Tempo tokens in output.
- Use
drag setup --from-env --dry-runto validate unattended configuration without writing it.
Output contract
Successful JSON uses {"ok":true,"data":...}. Errors use {"ok":false,"error":{"code":...,"message":...}} on stderr. Treat exit code 2 as invalid input or usage and exit code 1 as a runtime failure.
Portable recipes
| Recipe | Description |
|---|---|
recipe-log-coding-session | Log one completed coding session with Drag. Use when the user asks an agent to turn trustworthy session, repository, Git, and issue evidence into one reviewed Tempo worklog. |
recipe-audit-day | Audit one day of Tempo worklogs with Drag. Use when the user asks for a read-only, evidence-qualified daily review and proposed corrections. |
recipe-audit-week | Audit one week of Tempo worklogs with Drag. Use when the user asks for a read-only weekly review of daily totals, issue allocation, evidence, and proposed corrections. |
recipe-correct-worklog | Correct one Tempo worklog with Drag. Use when the user asks to replace an exact numeric worklog ID through an explicitly authorized, create-first non-atomic workflow. |
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.