github

Perform authenticated GitHub operations via the gh CLI using a provider token.

15|6|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/CloudChef/atlasclaw-providers --skill github-cloudchef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github
Source: https://github.com/CloudChef/atlasclaw-providers/tree/main/providers/github/skills/github
Command: npx skills add https://github.com/CloudChef/atlasclaw-providers --skill github-cloudchef

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Users need to perform GitHub operations securely from AtlasClaw using a non-interactive token and provider-managed context, avoiding manual gh auth in interactive sessions.

Core Features & Use Cases

  • Authenticated GitHub operations through the gh CLI using a configured provider instance and the user's GitHub token.
  • Supports common tasks such as PR checks, workflow runs, issues, repository queries, and API calls against GitHub.com or enterprise hosts.
  • Real-world use case: inspect a PR's checks or fetch PR details programmatically via the GitHub API within a provider-safe, non-interactive session.

Quick Start

Execute a GitHub command via gh for the configured provider instance to view PR checks.

Frequently Asked Questions about github

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run authenticated GitHub operations non-interactively via the gh CLI?

To run authenticated GitHub operations non-interactively via the gh CLI, use a configured provider instance with a user token. This setup allows you to execute commands like PR checks or API queries safely without manual gh auth sessions.

Can I use the gh CLI to check pull request status in an automated workflow?

Yes, you can use the gh CLI to check pull request status in an automated workflow. The Skill performs authenticated GitHub operations to inspect PR checks and fetch details programmatically within a provider-safe session.

Does this approach support GitHub Enterprise hosts or only GitHub.com?

This approach supports both GitHub.com and GitHub Enterprise hosts. It resolves the target enterprise host dynamically using the GH_HOST environment variable alongside your configured provider instance and user token.

What is needed to query the GitHub API for repository management without interactive login?

Querying the GitHub API for repository management without interactive login requires a configured provider instance with a valid user token. This enables safe, non-interactive GitHub operations with configured timeouts.

Why do my automated gh CLI commands timeout during workflow runs?

Automated gh CLI commands timeout during workflow runs because the Skill enforces non-interactive operation with safe timeouts. You must ensure your provider instance is properly configured with a user token to handle these session limits.

What's the best way to trigger workflow runs programmatically using the GitHub API?

The best way to trigger workflow runs programmatically using the GitHub API is through a configured provider instance using a user token. This method executes authenticated GitHub operations safely across GitHub.com or enterprise hosts.