Add activate grid skill

[JasonCWang]

No description provided.

[JasonCWang]

• Add activate grid skill #147 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR adds a new Claude skill documentation file for activating Grid API access, describing the intended interactive flow, required inputs, and expected outcomes. The change is isolated to .claude/skills/grid-api/SKILL.md and does not modify runtime code paths; its main impact is on developer/operator usability when running the skill via Claude Code.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk (documentation-only change).
• Only a skill documentation file is modified; there are no code, schema, or dependency changes. With the previously noted formatting/clarity nits addressed, risk is limited to developer experience and correctness of instructions.
• .claude/skills/grid-api/SKILL.md (ensure formatting and instructions match actual usage)

Important Files Changed

Filename	Overview
.claude/skills/grid-api/SKILL.md	Adds documentation for the activate-grid skill; no code changes, but ensure instructions are internally consistent and formatting is clean.

Sequence Diagram

sequenceDiagram
    participant User
    participant Claude as "Claude Code"
    participant Skill as "activate-grid skill"
    participant FS as "Local filesystem"
    participant Grid as "Grid API"

    User->>Claude: Invoke activate grid skill
    Claude->>Skill: Run skill
    Skill->>FS: Detect existing config/setup
    alt Config exists
        Skill->>FS: Load config
    else Missing config
        Skill->>User: Prompt for required fields
        User-->>Skill: Provide values
        Skill->>FS: Save config
    end
    Skill->>Grid: Call activation/auth endpoint
    Grid-->>Skill: Success or error
    Skill-->>Claude: Return status + guidance
    Claude-->>User: Display result

Loading

[greptile-apps]

_{2 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

_{1 file reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Incorrect skip condition

The instruction “If both show [set], skip to Step 4” is incorrect because Step 1 prints three lines and only two can ever show [set] (Token ID + Client Secret); the Base URL line prints the URL value even when unset. This makes the “both show” condition impossible to satisfy as written and will confuse users following the setup flow. Consider rephrasing to explicitly key off the two required vars (e.g., “If Token ID and Client Secret show [set], …”).

Prompt To Fix With AI

This is a comment left during a code review.
Path: .claude/skills/grid-api/SKILL.md
Line: 71:71

Comment:
**Incorrect skip condition**

The instruction “If both show `[set]`, skip to Step 4” is incorrect because Step 1 prints three lines and only two can ever show `[set]` (Token ID + Client Secret); the Base URL line prints the URL value even when unset. This makes the “both show” condition impossible to satisfy as written and will confuse users following the setup flow. Consider rephrasing to explicitly key off the two required vars (e.g., “If Token ID and Client Secret show `[set]`, …”).

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

Unsafe sourcing guidance

source ./setup-grid-credentials.sh executes an arbitrary local script with the user’s shell privileges. For a repo doc, this is risky guidance unless the script is guaranteed to be created by this project and its expected contents are verified. At minimum, the instructions should constrain this to a trusted, repo-provided script (or replace with an explicit export ... flow) so users don’t copy/paste a command that runs an unknown file.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .claude/skills/grid-api/SKILL.md
Line: 81:83

Comment:
**Unsafe sourcing guidance**

`source ./setup-grid-credentials.sh` executes an arbitrary local script with the user’s shell privileges. For a repo doc, this is risky guidance unless the script is guaranteed to be created by this project and its expected contents are verified. At minimum, the instructions should constrain this to a trusted, repo-provided script (or replace with an explicit `export ...` flow) so users don’t copy/paste a command that runs an unknown file.

How can I resolve this? If you propose a fix, please make it concise.