agentsclimarketplace
Sign in

Jira estimator

Skill ngocsangyem/MeowKit/.claude/skills/jira-estimator

Heuristic story-point estimation for a single Jira ticket via the jira-estimator agent. Read-only. Triggers: 'estimate KEY', 'story points for KEY', 'how complex is KEY'. NOT for complexity-only analysis (mk:jira-evaluator); NOT for full RCA (mk:jira-analyst).From its SKILL.md

Install
npx -y skills add ngocsangyem/MeowKit --skill jira-estimator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 15 stars15 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

1.9 KB, 316 tokens by cl100k_base, as published. Nobody here has run it

mk:jira-estimator

Forks to the jira-estimator agent. Read-only heuristic estimation. If a prior mk:jira-evaluator report exists at tasks/reports/jira-evaluate-*-{KEY}.md, the agent reads it and incorporates the complexity signals.

Triggers

  • "estimate PROJ-123"
  • "story points for PROJ-123"
  • "how complex is PROJ-123 in points?"

Examples

  • Cold estimate: "estimate PROJ-456 — give me a Fibonacci range and reasoning."
  • Post-evaluate: "I just evaluated PROJ-456; now estimate it."

See also

  • Agent: ../../agents/jira-estimator.md
  • Shared: ../jira/references/{install-and-auth,cli-idioms,safety-framework,estimation-guide}.md
  • Domain refs (cross-link, lives under jira-time):
    • ../jira-time/references/estimation-guide.md — story-point vs hours-based estimation tradeoffs
  • Peer intelligence: mk:jira-evaluator (run first for complexity signals), mk:jira-analyst (full ticket synthesis)
  • Peer execution: mk:jira-issue (update --custom-fields '{"customfield_10016": N}' writes the estimate), mk:jira-fields (discover instance-specific story-points field ID), mk:planning-engine (capacity analysis)

Gotchas

  • (none yet)

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most research analysis skills give in 316 tokens

Counted across 1,063 of the 1,754 authors here whose files we hold, read 2026-08-07

  • Generate a markdown reportin 32 of 1063, across 23 files
  • Cite each claim's sourcein 30 of 1063, across 15 files
  • Define the ideal customer profilein 20 of 1063, across 2 files
  • Search for companies matching the criteriain 20 of 1063, across 2 files
  • Assign a fit score from one to tenin 20 of 1063, across 2 files
  • Analyze the codebase to understand the productin 19 of 1063, across 1 file
  • Ask clarifying questions about the value propositionin 19 of 1063, across 1 file
  • Look for signals of immediate needin 19 of 1063, across 1 file
  • Identify the target decision maker rolein 19 of 1063, across 1 file
  • Suggest a personalized contact strategyin 19 of 1063, across 1 file
  • Provide conversation starters for outreachin 19 of 1063, across 1 file
  • Format results in a scannable markdown templatein 19 of 1063, across 1 file

Said here and by no other author read

  • fork to jira-estimator agent
  • read prior jira-evaluator report if it exists
  • incorporate complexity signals from prior reports
  • perform read-only heuristic estimation
  • provide a fibonacci range and reasoning
  • run jira-evaluator first for complexity signals

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.

Keep looking

Skills are one crate of 326,871. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.