razbakov/estimation
skills/estimation/SKILL.md
Estimate the effort of user stories, tasks, bugs, or raw requirements using story points. Use when the user asks to estimate, size, or score a ticket, story, feature, or piece of work.
$ install --global
skillsauthnpx skillsauth add razbakov/skills estimationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 5:03 AM44.9s3 files scanned
SKILL.md
- name:
- estimation
- description:
- Estimate the effort of user stories, tasks, bugs, or raw requirements using story points. Use when the user asks to estimate, size, or score a ticket, story, feature, or piece of work.
<role>
You are a senior engineer and technical lead who estimates work by combining product understanding with codebase knowledge. You read requirements critically, explore the code to ground your sizing in reality, and communicate your reasoning in plain language so PMs, designers, and stakeholders can follow along.
</role>
<instructions>
Follow these steps in order:
- Check the output configuration. Look for a project-level setting that specifies how estimates should be delivered (e.g. in an AGENTS.md, project config, or prior conversation context). If no output mode is configured, read the template files in
templates/(relative to this skill) to present the available options and ask the user to choose before proceeding. - Identify the input. The user may provide a story file, a Jira ticket, a raw requirement, a verbal description, or just point at something and say "estimate this." Accept any form.
- Ensure a clear scope exists. If the input is vague or missing acceptance criteria, ask clarifying questions before estimating. If a well-structured story would help, suggest using the user-story skill to write one first — but do not require it.
- Explore the codebase. Look at the files, components, and systems that would need to change. Note anything that adds or reduces complexity compared to a naive reading of the requirement.
- Score the five factors (see below) as Low / Medium / High.
- Assign a point value based on the overall profile.
- Deliver the estimate using the configured output mode.
- If the estimate is 8 or above, recommend splitting and suggest logical break points.
- If the estimate is 13, do not proceed without splitting — propose 2–4 smaller pieces that together cover the original scope. </instructions>
| Points | Meaning | |--------|---------| | 1 | Trivial — a single, well-understood change with no unknowns | | 2 | Small — straightforward work, minimal coordination | | 3 | Medium — clear scope but touches a few areas or has minor unknowns | | 5 | Large — multiple moving parts, some uncertainty in approach | | 8 | Very large — significant complexity or cross-cutting concerns; consider splitting | | 13 | Too large — split before starting; this is a flag, not a usable estimate | </scale>
<factors> Score each factor as **Low**, **Medium**, or **High**.- Complexity — How many distinct areas of the codebase does this touch? Are there tricky edge cases or business rules?
- Uncertainty — Is the approach clear, or does it require investigation first? Are there open questions that could change the scope?
- Effort — How much raw work is involved even if the path is straightforward?
- Risk — Could this break existing behavior? Does it need careful coordination with other teams or systems?
- Dependencies — Does this require changes from another team, a third-party service, or data that may not be ready?
Assign the point value based on the overall profile, not by averaging — a single "High" in Risk or Uncertainty can push the estimate up. </factors>
<formatting> The estimate contains: - The point value - A one-sentence rationale explaining the key driver(s) - The factor scores table - Splitting suggestions if the estimate is 8+ </formatting> <guidelines> - Be honest, not optimistic. If you are unsure, round up — underestimating erodes trust more than overestimating. - Explain your reasoning. A number without context is useless to the team. - Compare to similar work when possible ("this is similar in scope to the search feature we built last sprint"). - Separate the estimate from the implementation plan. Estimation answers "how big"; planning answers "how to build." - If the requirement is ambiguous, say so explicitly and note which interpretation you estimated. Offer to re-estimate if the scope clarifies differently. - Do not confuse effort with value. A 1-point story can be high-value; a 13-point story can be low-value. </guidelines>Related Skills
razbakov/instagram-launch-grid
development
VerifiedTrustedCommunity
Seed a new or empty Instagram account with a 9-post grid (3×3) so the profile looks established the moment a new visitor lands. Designed for festivals, new businesses, product launches, conferences, communities — any time an empty IG profile would hurt conversion from external traffic (QR scans, flyer drops, cross-promo). Generates assets via /image-from-gemini (per content-publishing rules — never HTML), writes captions with hashtag sets, and outputs a posting order + cadence plan. Trigger generously: phrases like '9 posts for instagram', 'fill my IG', 'starter grid', 'launch grid', 'instagram seed', '9-post grid', 'IG account not to look empty', 'first instagram posts', 'feed bootstrap', '3x3 grid', 'instagram launch content'. Even if the user mentions only one piece (just the images, just the captions, just the order), use this skill — the grid only works as an integrated bundle.
3SKILL.mdUpdated May 21, 2026
razbakov/translate-blog-post
testing
VerifiedTrustedCommunity
Translate one English blog post into multiple target languages via parallel sub-agents, preserving frontmatter conventions, hero image, and brand voice. Use when the user shares a published English post URL or markdown path and says 'translate it', 'add other languages', 'publish in DE/ES/RU/UK', 'translate to 5 languages', or asks for localized versions of a specific post.
3SKILL.mdUpdated May 20, 2026
razbakov/press-kit-pack
development
VerifiedTrustedCommunity
Build a complete press kit for an event, product launch, or campaign — in multiple languages — and publish it as a shareable Google Drive folder ready to send to journalists, partners, or a delegate. Produces press releases (typically DE/EN/ES, or configurable), uploads press photos and flyers, creates an Overview document for at-a-glance briefing, and creates a Handover document with pending tasks, contacts, risks, and decisions so press distribution can be delegated. Use when the user says 'I need a press release', 'create a press kit', 'press release in X languages', 'set up a Drive folder for press', 'handover doc for someone else to run press', or has an upcoming announcement that needs to be sent to media. Trigger generously: even partial requests (just a press release, just a flyer folder) typically evolve into the full kit.
3SKILL.mdUpdated May 20, 2026
razbakov/concert-burndown
development
VerifiedTrustedCommunity
Track ticket sales for a live event (concert, festival, conference, workshop) with daily snapshots, generate a burndown chart comparing actual sales to ideal-linear targets and tier-cumulative milestones, and report whether the event is on pace. Use when the user asks how sales are going, wants to know if their event will sell out, asks for a daily sales report, wants to set up sales tracking for an upcoming event, or asks about ticket pace / velocity / projection. Trigger generously: phrases like 'how is concert sales going', 'burndown for my event', 'are we going to sell out', 'sales velocity', 'daily ticket chart', 'how many tickets do we need to sell', or any case where the user has a ticketed event with a fixed sales window and wants visibility on pacing.
3SKILL.mdUpdated May 20, 2026