Menu
Read-only GitHub inspection via gh CLI (repos, issues, PRs, releases, actions, search).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
This skill provides comprehensive instructions for interacting with the Notion API via REST calls. This skill should be used whenever the user asks to interact with Notion, including reading, creating, updating, or deleting pages, databases, blocks, comments, or any other Notion content. The skill covers authentication, all available endpoints, pagination, error handling, and best practices.
UI/UX design system and implementation guidance for web and mobile products, with searchable recommendations for styles, color palettes, typography, UX rules, charts, icons, and stack-specific best practices. Use when users ask to design, build, review, improve, or fix interfaces such as landing pages, dashboards, product pages, forms, mobile screens, or design systems, especially when fast guidance is needed for HTML/Tailwind, React, Next.js, Astro, Vue, Nuxt, Svelte, SwiftUI, React Native, Flutter, shadcn/ui, Nuxt UI, or Jetpack Compose.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.
Detect secrets and credentials before they leak into git. Use this skill when: (1) About to commit code — scan staged files for API keys, tokens, passwords, private keys (2) User mentions secrets, credentials, API keys, tokens, .env, or sensitive data (3) User asks to "check secrets", "audit security", "review for leaks" (4) User asks about .gitignore coverage for sensitive files (5) Before creating a PR or push — final safety check Trigger phrases: "check for secrets", "scan for leaks", "is this safe to commit", "audit .gitignore", "any credentials exposed", "secrets", "confidential".
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends the agent's capabilities with specialized knowledge, workflows, or tool integrations.
| name | github-cli |
| description | Read-only GitHub inspection via gh CLI (repos, issues, PRs, releases, actions, search). |
Use this skill when you need to inspect GitHub data (list/view/search/fetch) without making changes:
Do not use when the user wants to create/edit/merge/close/delete anything.
list, view, status, search, api -X GET).create, edit, close, merge, delete, run, enable, disable, secret/variable set, repo fork/create/delete).gh api, force -X GET. For GraphQL, use query only and never mutation.GITHUB_PERSONAL_ACCESS_TOKEN in the environment. If missing, ask the user to set it.gh auth status -h github.comecho "$GITHUB_PERSONAL_ACCESS_TOKEN" | gh auth login -h github.com --with-token--repo OWNER/REPO.--json + --jq for stable parsing.--limit for list commands and paginate with gh api --paginate when needed.gh help or gh <cmd> -h to confirm a command is read-only before running it.references/gh-readonly.md for a categorized command map and examples.