Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

MichaelYochpaz

@michaelyochpaz source repo

4 published skills

  1. ▌
    Gh CLI · michaelyochpaz bundle
    GitHub CLI (`gh`) for GitHub and GitHub Enterprise workflows: inspect remote repositories and source, search code, investigate pull requests, issues, and Actions, work with releases and discussions, and call REST or GraphQL APIs. Use when the task requires `gh` or remote GitHub state. Do not use for local-only Git or workspace work.
    0
    installs
  2. ▌
    Glab CLI · michaelyochpaz bundle
    GitLab CLI (glab) for interacting with GitLab from the command line. Covers repositories, issues, merge requests, CI/CD pipelines, releases, and the GitLab API. Use when performing any GitLab-related operation, managing CI/CD pipelines and jobs, working with merge requests, or when the user mentions GitLab, glab, MRs, pipelines, .gitlab-ci.yml, projects, or groups.
    0
    installs
  3. ▌
    Acli Jira · michaelyochpaz bundle
    Atlassian CLI (acli) for Jira Cloud. View issues, search with JQL, navigate issue hierarchy (parents, children, epic contents), read comments, list attachments and links, and modify issues (comment, transition, edit, assign, link, create). Use when the user mentions Jira tickets, issues, stories, epics, bugs, tasks, spikes, JQL queries, or references a Jira issue key (e.g., "PROJ-123"). Also use for sprint context, board queries, or any Jira Cloud interaction.
    0
    installs
  4. ▌
    Playwright CLI · michaelyochpaz bundle
    Browser automation via playwright-cli for coding agents. Open browsers, navigate pages, take accessibility snapshots, interact with elements including canvas and WebGL content, capture screenshots, inspect network and console, manage cookies and storage, and generate Playwright test code. Use when the user mentions browser testing, web page inspection, taking screenshots, investigating page elements, UI testing, end-to-end testing, web scraping, data extraction, userscripts, or any browser-based interaction. Do not use for ordinary execution of existing Playwright test suites (use npx playwright test) or simple static page fetching. Use for interactive test debugging, authoring, or healing when browser inspection or control is needed.
    0
    installs