Connect Apps with Composio
ComposioHQ/awesome-claude-skills
Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.
Generates a deeply contextual, progressive-disclosure briefing for any GitHub repository.
Install GitHub Codebase Briefing
$ npx skills add google-labs-code/stitch-sdk --skill github-codebase-briefing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install google-labs-code/stitch-sdk github-codebase-briefing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/google-labs-code/stitch-sdk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/repo-review .claude/skills/github-codebase-briefing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "github-codebase-briefing" agent skill from https://github.com/google-labs-code/stitch-sdk/tree/main/.agents/skills/repo-review into .claude/skills/github-codebase-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-codebase-briefing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/google-labs-code/stitch-sdk/tree/main/.agents/skills/repo-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add google-labs-code/stitch-sdk --skill github-codebase-briefing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install google-labs-code/stitch-sdk github-codebase-briefing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/google-labs-code/stitch-sdk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/repo-review .agents/skills/github-codebase-briefing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "github-codebase-briefing" agent skill from https://github.com/google-labs-code/stitch-sdk/tree/main/.agents/skills/repo-review into .agents/skills/github-codebase-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-codebase-briefing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add google-labs-code/stitch-sdk --skill github-codebase-briefing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install google-labs-code/stitch-sdk github-codebase-briefing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/google-labs-code/stitch-sdk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/repo-review .cursor/skills/github-codebase-briefing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "github-codebase-briefing" agent skill from https://github.com/google-labs-code/stitch-sdk/tree/main/.agents/skills/repo-review into .cursor/skills/github-codebase-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-codebase-briefing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/google-labs-code/stitch-sdk.git --path .agents/skills/repo-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add google-labs-code/stitch-sdk --skill github-codebase-briefing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install google-labs-code/stitch-sdk github-codebase-briefing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/google-labs-code/stitch-sdk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/repo-review .gemini/skills/github-codebase-briefing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "github-codebase-briefing" agent skill from https://github.com/google-labs-code/stitch-sdk/tree/main/.agents/skills/repo-review into .gemini/skills/github-codebase-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-codebase-briefing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install google-labs-code/stitch-sdk github-codebase-briefingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add google-labs-code/stitch-sdk --skill github-codebase-briefing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/google-labs-code/stitch-sdk.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/repo-review .github/skills/github-codebase-briefing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "github-codebase-briefing" agent skill from https://github.com/google-labs-code/stitch-sdk/tree/main/.agents/skills/repo-review into .github/skills/github-codebase-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-codebase-briefing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add google-labs-code/stitch-sdk --skill github-codebase-briefing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install google-labs-code/stitch-sdk github-codebase-briefing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/google-labs-code/stitch-sdk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/repo-review .opencode/skills/github-codebase-briefing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "github-codebase-briefing" agent skill from https://github.com/google-labs-code/stitch-sdk/tree/main/.agents/skills/repo-review into .opencode/skills/github-codebase-briefing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-codebase-briefing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
github-codebase-briefing- GitHub stars
- 1.8k
- Token cost
- ~887 tokens
- SKILL.md length
- 382 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generates a deeply contextual, progressive-disclosure briefing for any GitHub repository.
- Works in 4 steps: Initialize the Mental Model → Retrieve State & Delta → Deep Analysis Logic → …
- Asked for a GitHub report
- SKILL.md covers Prerequisites, Instructions and Output Template
- Calls gh
What it does
GitHub Codebase Briefing is an agent skill from google-labs-code/stitch-sdk, published by the product's own GitHub organization. Generates a deeply contextual, progressive-disclosure briefing for any GitHub repository. It builds a mental model of the code before analyzing issues and PRs to provide actionable insights. Use when asked for a "GitHub report," "repo status," "daily briefing," or to "catch up on a codebase."
Its SKILL.md is about 890 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires GitHub CLI (gh) authenticated and installed.
It sits in Productivity & Automation. It works with GitHub. The repository describes itself as: Generate UI screens from text prompts and extract their HTML and screenshots programmatically. The licence is MIT.
When your agent uses it
- Asked for a GitHub report
- Catch up on a codebase
Example prompts
- “GitHub report,”
- “repo status,”
- “daily briefing,”
- “/github-codebase-briefing”
Requirements
- Compatibility (from SKILL.md): Requires GitHub CLI (gh) authenticated and installed.
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit e3f8ece. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires GitHub CLI (gh) authenticated and installed.
From compatibility in the SKILL.md frontmatter.
Context cost
GitHub Codebase Briefing loads about 887 tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 382 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from google-labs-code/stitch-sdk at commit e3f8ece, republished under its MIT licence (© google-labs-code). 382 words, ~887 tokens.
Download SKILL.mdSave it as
.claude/skills/github-codebase-briefing/SKILL.md (or your agent's skills folder).- name
- github-codebase-briefing
- description
- Generates a deeply contextual, progressive-disclosure briefing for any GitHub repository. It builds a mental model of the code before analyzing issues and PRs to provide actionable insights. Use when asked for a "GitHub report," "repo status," "daily briefing," or to "catch up on a codebase."
- compatibility
- Requires GitHub CLI (gh) authenticated and installed.
- license
- MIT
GitHub Codebase Briefing
This skill performs a "deep read" of a repository. It avoids superficial listings by first understanding the project's architecture and then evaluating open items against that context.
Prerequisites
- Tooling: The agent must have access to the
ghCLI. - Auth: The user must be authenticated (
gh auth status).
Instructions
Step 1: Initialize the Mental Model
Before looking at tasks, understand the environment. Run these commands in sequence:
- Metadata:
gh repo view <owner/repo> --json name,description,stargazerCount,forkCount - Structure:
gh api repos/<owner/repo>/contents/ - Identity: Read the project manifest (e.g.,
package.json,go.mod,pyproject.toml) andREADME.md. - Entry Point: Read the primary entry file (e.g.,
index.ts,main.go) to identify the Public API surface.
Step 2: Retrieve State & Delta
Fetch current items and recent changes:
- Issues:
gh issue list --repo <owner/repo> --state open --json number,title,body,author,createdAt,updatedAt,labels,comments - PRs:
gh pr list --repo <owner/repo> --state open --json number,title,body,author,createdAt,updatedAt,labels,additions,deletions,changedFiles,headRefName - 24h Delta:
gh issue list --state closed --since 24handgh pr list --state merged --since 24h.
Step 3: Deep Analysis Logic
For every issue and PR, do not just summarize the text. Perform a logic check:
- Issues: Use
gh api repos/<owner/repo>/contents/<path>to inspect the code mentioned in the report. - PRs: Use
gh pr diff <number>to review actual implementation. Evaluate if the code follows the patterns found in Step 1. - Flags:
- 🚨 SECURITY: Scan for credentials, auth bypass, or injection keywords.
- 🤝 EXTERNAL: Prioritize PRs from non-maintainers.
- ✅ READY: Verify mergeability with
gh pr view <number> --json mergeable,statusCheckRollup.
Show full SKILL.md (141 more words)Show less
Step 4: Pattern Synthesis
Group items into high-level insights:
- Bug Clusters: Identify if 3+ issues share a root cause in a specific module.
- Hot Modules: Flag files that appear in multiple open items.
- Client Patterns: Group issues by consumer (e.g., "VS Code users are reporting X").
Output Template
# {REPO_NAME} Daily Briefing — {DATE}
Snapshot: {N} Issues ({+X} since yesterday) | {M} PRs ({+Y} since yesterday)
⚡ Suggested Actions Today
- [Priority] #{Num}: {One-line reason}
- [Priority] #{Num}: {One-line reason}
📂 Open Issues Deep Dive
[Flag] #{Num} — {Title}
- Context: Plain-English explanation of the "why" and "where" in the codebase.
- Key Evidence: > {Blockquote of critical user text}
- Resolution Path: {Quick fix/Design decision/Blocked}
🔀 Pull Request Analysis
[Flag] #{Num} — {Title}
- Impact: Summary of files changed and architectural fit.
- Quality Note: Honest assessment of implementation and CI status.
🔍 Patterns & Health
- Hot Modules:
{list/of/files} - Release Cadence: Last release was
{days}ago.
© google-labs-code, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/repo-review of google-labs-code/stitch-sdk.
Open the folder on GitHubat commit e3f8ece
Compare with similar skills
GitHub Codebase Briefing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| GitHub Codebase Briefing this skillgoogle-labs-code/stitch-sdk | 1.8k | — | ~887 | Automated safety check: Pass | MIT | |
| Connect Apps with ComposioComposioHQ/awesome-claude-skills | 77k | 3 repos | ~557 | Automated safety check: Pass | None | |
| Daily BriefingRion-Wu-tech/ai-daily-briefing | 174 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Superset Automatesuperset-sh/superset | 15k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Ingestcoreyhaines31/makerskills | 844 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Composio Cloud Toolsquarqlabs/argus | 277 | — | ~543 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Daily Briefing
Rion-Wu-tech/ai-daily-briefing
Generate a source-linked Chinese AI/Web3 daily briefing with official model releases, infrastructure, application adoption, funding, and cross-industry signals directly in Codex, then save the…
Superset Automate
superset-sh/superset
Turns a recurring chore into a scheduled or event-triggered Superset agent, drafting its prompt, picking a target and trigger, and reviewing the first run.
Ingest
coreyhaines31/makerskills
When you paste raw human input — a call transcript (Grain, Zoom, Granola, Fathom), a text or email from a client/partner/friend, a voice-memo dump, or meeting notes — and want it converted into…
Composio Cloud Tools
quarqlabs/argus
Routes requests to external SaaS apps such as GitHub, Gmail, Google Calendar, Slack, Notion and Linear through cloud tools, with safeguards on irreversible actions.
Clawdi
Clawdi-AI/clawdi
API keys, tokens, memory, sessions, Projects, integrations. An agent skill from Clawdi-AI/clawdi.
More from google-labs-code/stitch-sdk
All 9 skills in this repo- Official
Stitch SDK Development
google-labs-code/stitch-sdk
Develop the Stitch SDK. An agent skill from google-labs-code/stitch-sdk.
- Official
Stitch SDK Domain Design
google-labs-code/stitch-sdk
Design the domain model for the Stitch SDK. An agent skill from google-labs-code/stitch-sdk.
- Official
Stitch SDK Pipeline
google-labs-code/stitch-sdk
Run the full Stitch SDK generation pipeline. An agent skill from google-labs-code/stitch-sdk.
- Official
Stitch SDK Readme
google-labs-code/stitch-sdk
Generate or update the README for the Stitch SDK. An agent skill from google-labs-code/stitch-sdk.
- Official
Stitch SDK Usage
google-labs-code/stitch-sdk
Use the Stitch SDK to generate, edit, and iterate on UI screens from text prompts, manage projects, and retrieve screen HTML/images.
- Official
TDD Red Green Refactor
google-labs-code/stitch-sdk
Enforces a disciplined Red-Green-Refactor (TDD) workflow in TypeScript/Node.js.
Related
Works with
Categories
Questions about GitHub Codebase Briefing
What does GitHub Codebase Briefing do?
Generates a deeply contextual, progressive-disclosure briefing for any GitHub repository. GitHub Codebase Briefing is an agent skill from google-labs-code/stitch-sdk, published by the product's own GitHub organization. Generates a deeply contextual, progressive-disclosure briefing for any GitHub repository.
When should I use GitHub Codebase Briefing?
GitHub Codebase Briefing fits situations like: asked for a GitHub report; catch up on a codebase.
How do I install GitHub Codebase Briefing in Claude Code?
Run `npx skills add google-labs-code/stitch-sdk --skill github-codebase-briefing -a claude-code`. Or copy the skill folder (.agents/skills/repo-review in google-labs-code/stitch-sdk) into .claude/skills/github-codebase-briefing in your project. Claude Code loads it when a task matches its description.
How do I install GitHub Codebase Briefing in Codex?
Run `npx skills add google-labs-code/stitch-sdk --skill github-codebase-briefing -a codex`. Or copy the skill folder (.agents/skills/repo-review in google-labs-code/stitch-sdk) into .agents/skills/github-codebase-briefing in your project. Codex loads it when a task matches its description.
Can I use GitHub Codebase Briefing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add google-labs-code/stitch-sdk --skill github-codebase-briefing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-codebase-briefing, .gemini/skills/github-codebase-briefing, .github/skills/github-codebase-briefing and .opencode/skills/github-codebase-briefing in your project.
What does GitHub Codebase Briefing need to run?
Going by SKILL.md and its folder, GitHub Codebase Briefing needs the command-line tools its instructions call (gh). Compatibility (from SKILL.md): Requires GitHub CLI (gh) authenticated and installed..
Does GitHub Codebase Briefing access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is GitHub Codebase Briefing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does GitHub Codebase Briefing use?
GitHub Codebase Briefing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does GitHub Codebase Briefing use?
About 887 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to GitHub Codebase Briefing?
Skills that share tags, products or a category with GitHub Codebase Briefing: Connect Apps with Composio (ComposioHQ/awesome-claude-skills, 77k stars), Daily Briefing (Rion-Wu-tech/ai-daily-briefing, 174 stars), Superset Automate (superset-sh/superset, 15k stars) and Ingest (coreyhaines31/makerskills, 844 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GitHub Codebase Briefing?
google-labs-code (a GitHub organization, an official publisher) maintains it in google-labs-code/stitch-sdk, which has 1,825 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 1, 2026.
Source: google-labs-code/stitch-sdk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.