Files
fce9bd8f96 Agent tooling relocation, architecture redesign docs (#3343)
* add export for address txs

* transfer all export from page to dialog

* remove old route and components

* improve file name and fix loading state of icon button

* basic implementation

* refetch item status

* status indicator for download items

* changes for multichain

* handle too many requests for downloads error

* update button styles and spacing

* fix tests

* disable async export for multichain

* Fix CSV export cancel flow and stabilize context updates

Applied via @cursor push command

* test and review fixes

* move file to client folder

* round 3

* add glossary

* migration tasks and skill

* move skills to .agents folder

* rename migrate skill

* refine project rules

* move MIGRATION_TASKS.md to client directory

* update sym links

* refine migration skills

* fixes after merging the main branch

---------

Co-authored-by: Hanzo Dev <[email protected]>
2026-03-02 16:42:12 +02:00

1.4 KiB

name, description
name description
check-github-cli Ensure GitHub CLI (gh) is installed and authenticated before running gh commands; guide the user to configure it if not

Check GitHub CLI Availability

Use this skill whenever a workflow or command requires the GitHub CLI (gh). Before running any gh commands:

  1. Check installation and auth: Run gh auth status. If it reports "not logged in" or the command is not found:
    • If gh is not installed: Ask the user to install it (e.g. brew install gh on macOS, or see GitHub CLI) and then authenticate.
    • If gh is installed but not configured: Ask the user to configure it themselves. Provide these instructions to help them:
      • Run gh auth login and follow the prompts (choose HTTPS or SSH, authenticate via browser or token).
      • Ensure the account has the permissions needed for the operation (e.g. read access to the repository, or read/write if the task requires it).
    • Do not attempt to authenticate on the user's behalf; only guide them with the commands and link to GitHub CLI authentication docs.
  2. If gh auth status succeeds: Proceed with the steps that require gh.

Other skills that depend on gh (e.g. get-checks-status) should instruct the agent to ensure GitHub CLI is ready first by following this skill.