Skip to content

feat: Add Grok Build skills directory support to gh skill #13846

Closed

Agent suggestions

Public preview

Description

@beingminimal

Here is a draft for your GitHub feature request, structured exactly as you requested.


Describe the feature or problem you’d like to solve

With the release of Grok Build, x.ai introduced native support for "Skills"—reusable folders containing markdown instructions, script files, and resources that help guide agent behavior. Currently, the gh skill CLI command extension does not recognize or support provisioning, managing, or interacting with Grok Build's custom skills structure (.grok/skills/ or ~/.grok/skills/).

As developers adopt Grok Build, managing these system-specific agent skills alongside existing workflows within GitHub CLI would streamline project onboarding and automation.

Proposed solution

We should update gh skill to detect, configure, and manage Grok Build skill folders. This will benefit the CLI and its users by:

  • Providing unified agent management: Allowing users to create, view, or link project-specific agent instructions directly via the CLI into the expected .grok/skills/ paths.
  • Streamlining workflow setup: Enabling automated scaffolding of .grok/ configuration trees when initializing repositories or adding agent-based development workflows.
  • Slash-command parity: Aligning with Grok's native capability where custom local skills dynamically surface as user-invocable slash commands (/<skill-name>).

Additional context

The core architectural specifications for how Grok handles skills, plugins, and configuration structures can be found directly in the official x.ai documentation:
https://docs.x.ai/build/features/skills-plugins-marketplaces#skills

Key Discovery Details from x.ai Docs:

  • Local repo skills are walked up to the repository root via: ./.grok/skills/
  • Global user-level skills reside at: ~/.grok/skills/
  • Grok also features deep backward compatibility with ~/.agents/skills/ and Claude Code rules, which gh skill could potentially map to or utilize as a fallback translation layer during local environment setup.

Activity

  1. beingminimal commented on Jul 11, 2026

    @beingminimal
    Author

    @BagToad Can you please assign this to copilot and get merged? Thanks

  2. cli-triage commented on Jul 11, 2026

    @cli-triage

    I'm suggesting the off-topic label for this issue. The request asks the GitHub CLI to integrate with Grok Build (x.ai's AI product) by managing .grok/skills/ directories - this is unrelated to the GitHub CLI's purpose, which is to interact with GitHub's platform and APIs. Additionally, gh skill is not an existing command in the gh CLI. No duplicates were found. A maintainer should confirm and close this as off-topic.

    Generated by Issue Triage (skills-driven) for #13846 · 21.7 AIC · ⌖ 5.49 AIC · ⊞ 5.1K · ◷

  3. github-actions commented on Jul 13, 2026

    @github-actions
    Contributor

    Thank you for your issue! We have categorized it as an enhancement (feature or improvement) request, and it has been added to our backlog. In doing so, we are not committing to implementing this feature at this time, but, we will consider it for future releases based on community feedback and our own product roadmap.

    Unless you see the help wanted Contributions welcome label, we are not currently looking for external contributions for this feature.

    If you come across this issue and would like to see it implemented, please add a thumbs up! This will help us prioritize the feature. Please only comment if you have additional information or viewpoints to contribute.

  4. self-assigned this
    on Jul 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementa request to improve CLIgh-skillrelating to the gh skill command

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions