Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

zeiynz

@zeiynz source repo

7 published skills

  1. ▌
    Resume Tailor · zeiynz bundle
    Tailor a resume to a specific job posting — rewrite bullet points to mirror the posting's language and priorities, reorder sections by relevance, and flag keyword gaps that would trip an ATS (applicant tracking system) filter. Use whenever the user shares a resume plus a job posting/description and asks to "tailor my resume", "optimize this for the job", "will this pass ATS", "rewrite my bullets for this role", or asks for feedback on a resume against a specific opportunity. Also trigger for general resume review even without a specific posting, defaulting to strong-generalist best practices.
    0
    installs
  2. ▌
    Changelog Generator · zeiynz bundle
    Generate a clean, user-facing changelog or release notes from raw git commit history, merged PR titles, or a diff between two versions/tags. Use whenever the user asks to "write release notes", "generate a changelog", "summarize what changed since v1.2", pastes a list of commit messages or PR titles, or is preparing a release and needs commits translated from developer-speak into something users/stakeholders can read. Also trigger when a user shares `git log` output directly.
    0
    installs
  3. ▌
    Sec Filing Analyzer · zeiynz bundle
    Extract, structure, and summarize SEC filings (10-K, 10-Q, 8-K, S-1) into research-ready formats — financial tables, risk factor deltas vs. prior filing, MD&A summaries, and insider-trading flags. Use this skill whenever the user mentions a ticker + filing type, pastes or links an SEC filing (EDGAR URL, accession number), asks to "summarize the 10-K", "what changed in the risk factors", "pull the financials from the latest 10-Q", or wants filing data turned into a structured research note. Also trigger for comparative filing analysis ("compare AAPL's last two 10-Ks") or building a filing-monitoring workflow.
    0
    installs
  4. ▌
    Competitive Teardown · zeiynz bundle
    Produce a structured competitive teardown of a SaaS/tech product — pricing model, feature matrix, positioning, ICP, GTM motion, and defensibility gaps. Use whenever the user asks to "research a competitor", "compare us to X", "what's [product]'s pricing", "build a battlecard", "how does [company] position itself", or wants a repeatable framework for evaluating competing products rather than a one-off summary. Also trigger when the user is deciding whether to build a feature that a competitor already ships and needs a build-vs-differentiate read.
    0
    installs
  5. ▌
    Meeting Action Items · zeiynz bundle
    Turn raw meeting notes, transcripts, or voice-memo dumps into structured decisions, action items (with owner + due date), and open questions — ready to paste into Slack, email, or a tracker. Use whenever the user pastes meeting notes/transcripts, says "extract action items from this", "summarize this call", "who owns what from this meeting", or uploads a transcript file and wants next steps rather than a narrative recap. Trigger proactively any time raw unstructured meeting text appears in the conversation, even if the user's ask is vague ("here's the notes from today").
    0
    installs
  6. ▌
    Github Readme Generator · zeiynz bundle
    Generate or overhaul a GitHub repository README by actually reading the codebase (package.json, entry points, existing docs, folder structure) rather than asking the user to describe their own project. Use whenever the user asks to "write a README", "document this repo", "improve my README", shares a repo/folder and wants documentation, or is about to open-source/publish a project and needs a portfolio-quality README. Also trigger when a repo is shared with no README at all and the user's goal involves sharing or publishing it.
    0
    installs
  7. ▌
    Frontend Component Audit · zeiynz bundle
    Audit a React/Next.js component or codebase for accessibility, performance, and consistency issues before shipping — checks re-render patterns, prop drilling depth, missing memoization, unhandled loading/error states, and WCAG violations. Use whenever the user shares a component file and asks to "review this", "is this production-ready", "why is this slow", "check this for accessibility", or before merging a PR that touches shared UI components. Also trigger proactively when generating new components if the user's codebase context suggests these standards apply (TypeScript strict mode, existing design system usage).
    0
    installs