Milestone issues
Manage issues within Gitea/Forgejo milestones — list, add, remove, progress tracking, burndown, bulk assign, and move between milestones.From its SKILL.md
npx -y skills add deevus/tea-skills --skill milestone-issuesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 5 stars5 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.
- runs commandsInstructs the agent to run 6 commands, including `tea milestones issues "v1.0" -o simple` and 5 more.
SKILL.md
1.7 KB, 446 tokens by cl100k_base, as published. Nobody here has run it
Milestone Issues
List / Add / Remove
tea milestones issues "v1.0" -o simple # list issues (recommended)
tea milestones issues "v1.0" --state all --kind issue # filter by state/kind
tea milestones issues "v1.0" --fields "index,title,state,assignees,labels"
tea milestones issues add "v1.0" 42 # assign issue
tea milestones issues remove "v1.0" 42 # unassign issue
Bulk Assign
# By label
tea issues list --labels "release:v1.0" --output json | \
jq -r '.[].index' | xargs -I{} tea milestones issues add "v1.0" {}
# By range
for i in $(seq 10 20); do tea milestones issues add "v1.0" $i; done
Progress Tracking
tea milestones list --output json | jq '.[] | {
title, open: .open_issues, closed: .closed_issues,
progress: (if (.open_issues + .closed_issues) > 0
then ((.closed_issues * 100) / (.open_issues + .closed_issues) | round | tostring) + "%"
else "0%" end)
}'
Burndown
for ms in $(tea milestones list --output json | jq -r '.[].title'); do
open=$(tea milestones issues "$ms" --state open --output json | jq length)
closed=$(tea milestones issues "$ms" --state closed --output json | jq length)
echo "$ms: $closed done, $open remaining"
done
Move Issues Between Milestones
tea milestones issues "v1.0" --state open --output json | \
jq -r '.[].index' | while read idx; do
tea milestones issues remove "v1.0" $idx
tea milestones issues add "v1.1" $idx
done
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most roadmap strategy skills give in 446 tokens
Counted across 614 of the 719 authors here whose files we hold, read 2026-09-06
- Check for product marketing context firstin 39 of 614, across 16 files
- Use compact with a custom summaryin 32 of 614, across 16 files
- Compact after planningin 30 of 614, across 16 files
- Do not compact mid-implementationin 30 of 614, across 17 files
- Structure launch marketing across three channel typesin 21 of 614, across 5 files
- Read the compaction suggestionin 20 of 614, across 10 files
- Write before compactingin 17 of 614, across 11 files
- Write important context to files before compactingin 16 of 614, across 5 files
- Recruit early users one-on-onein 16 of 614, across 3 files
- Identify 3-5 core content pillarsin 15 of 614, across 9 files
- Target a specific keyword or questionin 14 of 614, across 4 files
- Stagger announcements to maintain momentumin 14 of 614, across 4 files
Said here and by no other author read
- Remove issues from milestones
- Track milestone progress
- Calculate milestone burndown
- Move issues between milestones
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.