vslipchenko
UserStandalone plugins and skills for the AI domain.
Categories
Indexed Skills (12)
add
Add tickets to the estimator history by Jira key — fetched live from Jira and written as new records — without re-running `sync`. Use when the user wants to add / record specific tickets into the history (e.g. "add ABC-7777 to history", "add these tickets to the estimator history", "add missing tickets 7777, 7780"). Adds whole records (overrides an existing one only after confirmation); field-level editing is the edit skill.
edit
Edit fields of existing estimator history records, or delete records, selected by Jira key. Use when the user wants to change / fix / update a stored record's fields or remove records (e.g. "edit ABC-7777", "fix the story points on ABC-1", "delete ABC-2, ABC-3 from history"). Does NOT add new records.
estimate
Estimate a Jira ticket's story points using the team's historical dataset. Use when the user asks to estimate/size/point a ticket (e.g. "estimate ABC-7777", "how many points is this ticket", "estimate 7777", or pastes a Jira ticket link). Fetches the ticket via the Atlassian MCP, compares it to ~/.estimator history, suggests an estimate, then records the outcome.
export
Export / back up the estimator's stored dataset (history.csv, and optionally config.json) to a file path the user chooses. Use when the user wants to back up, export, snapshot, or copy out their estimation history (e.g. "export my history to ~/backups", "back up the estimator data", "save a copy of the history before resetting"). Counterpart to the import skill.
find
Look up one or more records in the estimator history by Jira key. Use when the user wants to find / show / inspect a stored ticket record (e.g. "find ABC-7777 in history", "show the record for 7777", "look up ABC-1, ABC-2").
import
Import an existing history CSV into the estimator from a file path, instead of building it with `sync`. Use when the user wants to load / import an existing estimation history (e.g. "import my history from ./history.csv", "load this dataset", "import estimator history"). Supports merging into or replacing the current history.
sync
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.
filter-translator
Convert a plain-text filter description into a syntactically correct expression in a target query/filter format — OData $filter, JQL, MongoDB, SQL WHERE, or RQL. Use when the user asks to turn a description into a filter/query (e.g. "convert this to a MongoDB filter", "give me the JQL for...", "as an OData $filter", "as an RQL query", "make a SQL WHERE clause for these conditions"). For OData/RQL, can also produce the RFC 3986 percent-encoded URL form on request. Always resolves field names, then confirms the resulting logical expression in plain text before producing the final syntax.
password-generator
Generate cryptographically secure passwords or diceware-style passphrases via a bundled CSPRNG script — never by having the model type out a "random-looking" string. Use when the user asks to generate/create a password, passphrase, secret, PIN, or random token, or to check the strength of one.
naturalize
Rewrite Claude-generated text so it matches the user's own personal writing voice, calibrated once via writing samples and a togglable checklist, then reused automatically on every later request. Use when the user asks to "naturalize" text, make it "sound like me" / "less like AI", "humanize" a draft, strip AI writing tells (em-dashes, curly quotes, stock phrases like "I hope this helps"), asks to (re)calibrate their writing-voice profile, or explicitly asks for a generic pass that ignores their profile ("naturalize this generically", "without my profile", "ignore my profile for this one").
dev-timesheet-report
Build a developer timesheet for a date range from real activity — local git repos, a ticket board (Jira), a wiki (Confluence), and code hosts (GitHub, GitLab, Bitbucket) — rendered in the terminal or as CSV, with each line showing the date, item type, id, title and an activity label (Coding, Code Review, Investigation, Testing, Documentation). Use when the user asks what they worked on, for a timesheet/activity/work report, to fill in timesheets or a standup/weekly summary, or to export their activity for a period. Configured once and stored, overridable per run.
akinator
Play an Akinator-style guessing game in either direction — the user thinks of a character, animal, or object and Claude asks yes/no questions to guess it, or Claude secretly picks one (committed up front with a salted SHA-256 hash, revealed and verifiable at the end) and the user asks the questions. Tracks a best/worst-run leaderboard per mode and question limit. Use when the user wants to play Akinator, 20 questions, "guess what I'm thinking", "think of something and I'll guess it", asks to see their Akinator leaderboard, or wants to add entries to their Akinator secret lists.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.