← all publishers

vslipchenko

@vslipchenko source repo

Report this profile Claim this profile

• 10 skills
• 0 followers
• 20 hours ago last updated

1. ▌
   Naturalize · vslipchenko bundle

   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").
   0
   installs
2. ▌
   Filter Translator · vslipchenko bundle

   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.
   2
   installs
3. ▌
   Password Generator · vslipchenko bundle

   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.
   0
   installs
4. ▌
   Add · vslipchenko

   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.
   0
   installs
5. ▌
   Edit · vslipchenko bundle

   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.
   0
   installs
6. ▌
   Find · vslipchenko bundle

   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").
   0
   installs
7. ▌
   Sync · vslipchenko

   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.
   0
   installs
8. ▌
   Export · vslipchenko

   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.
   1
   install
9. ▌
   Import · vslipchenko bundle

   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.
   0
   installs
10. ▌
    Estimate · vslipchenko

    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.
    0
    installs