Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
Scan project root for file tree, dominant languages, and LOC estimate.
Install Project Surface Scan
$ npx skills add digipulse-engineering/GAAI-framework --skill project-surface-scan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install digipulse-engineering/GAAI-framework project-surface-scan --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/digipulse-engineering/GAAI-framework.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.gaai/core/skills/cross/project-surface-scan .claude/skills/project-surface-scan && 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 "project-surface-scan" agent skill from https://github.com/digipulse-engineering/GAAI-framework/tree/main/.gaai/core/skills/cross/project-surface-scan into .claude/skills/project-surface-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-surface-scan", 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/digipulse-engineering/GAAI-framework/tree/main/.gaai/core/skills/cross/project-surface-scanType 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 digipulse-engineering/GAAI-framework --skill project-surface-scan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install digipulse-engineering/GAAI-framework project-surface-scan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digipulse-engineering/GAAI-framework.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.gaai/core/skills/cross/project-surface-scan .agents/skills/project-surface-scan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "project-surface-scan" agent skill from https://github.com/digipulse-engineering/GAAI-framework/tree/main/.gaai/core/skills/cross/project-surface-scan into .agents/skills/project-surface-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-surface-scan", 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 digipulse-engineering/GAAI-framework --skill project-surface-scan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install digipulse-engineering/GAAI-framework project-surface-scan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digipulse-engineering/GAAI-framework.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.gaai/core/skills/cross/project-surface-scan .cursor/skills/project-surface-scan && 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 "project-surface-scan" agent skill from https://github.com/digipulse-engineering/GAAI-framework/tree/main/.gaai/core/skills/cross/project-surface-scan into .cursor/skills/project-surface-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-surface-scan", 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/digipulse-engineering/GAAI-framework.git --path .gaai/core/skills/cross/project-surface-scan--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 digipulse-engineering/GAAI-framework --skill project-surface-scan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install digipulse-engineering/GAAI-framework project-surface-scan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digipulse-engineering/GAAI-framework.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.gaai/core/skills/cross/project-surface-scan .gemini/skills/project-surface-scan && 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 "project-surface-scan" agent skill from https://github.com/digipulse-engineering/GAAI-framework/tree/main/.gaai/core/skills/cross/project-surface-scan into .gemini/skills/project-surface-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-surface-scan", 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 digipulse-engineering/GAAI-framework project-surface-scanInstalls 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 digipulse-engineering/GAAI-framework --skill project-surface-scan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/digipulse-engineering/GAAI-framework.git skills-src && mkdir -p .github/skills && cp -r skills-src/.gaai/core/skills/cross/project-surface-scan .github/skills/project-surface-scan && 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 "project-surface-scan" agent skill from https://github.com/digipulse-engineering/GAAI-framework/tree/main/.gaai/core/skills/cross/project-surface-scan into .github/skills/project-surface-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-surface-scan", 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 digipulse-engineering/GAAI-framework --skill project-surface-scan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install digipulse-engineering/GAAI-framework project-surface-scan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/digipulse-engineering/GAAI-framework.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.gaai/core/skills/cross/project-surface-scan .opencode/skills/project-surface-scan && 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 "project-surface-scan" agent skill from https://github.com/digipulse-engineering/GAAI-framework/tree/main/.gaai/core/skills/cross/project-surface-scan into .opencode/skills/project-surface-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-surface-scan", 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
project-surface-scan- GitHub stars
- 163
- Token cost
- ~1.4k tokens
- SKILL.md length
- 438 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Scan project root for file tree, dominant languages, and LOC estimate.
- Works in 6 steps: Timed scan start → File tree walk → Extension frequency map → …
- Tasks that involve Observability
- SKILL.md covers Purpose / When to Activate, Exclusions (always skip), Process and Output Schema…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Project Surface Scan is an agent skill from digipulse-engineering/GAAI-framework. Scan project root for file tree, dominant languages, and LOC estimate. Produces structured baseline context for Stage 2 LLM synthesis during bootstrap. Respects .gitignore and standard exclusions. Outputs per-directory file counts, ranked language list, size class, and observability summary.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Works with any filesystem-based AI coding agent
It sits in DevOps & Cloud, covering Observability. The repository describes itself as: Turns AI coding tools into reliable software delivery systems. Drop a .gaai/ folder into any project — Discovery defines what to build, Delivery executes autonomously until…
When your agent uses it
- Tasks that involve Observability
Example prompts
- “/project-surface-scan”
Requirements
- Python 3
- Compatibility (from SKILL.md): Works with any filesystem-based AI coding agent
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Timed scan start
- File tree walk
- Extension frequency map
- Language detection
- LOC estimation
- Observability summary
What it can do on your machine
Read from SKILL.md and the folder at commit a26ea7a. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Works with any filesystem-based AI coding agent
From compatibility in the SKILL.md frontmatter.
Context cost
Project Surface Scan loads about 1.4k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 438 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 438 words (~1,426 tokens).
- name
- project-surface-scan
- compatibility
- Works with any filesystem-based AI coding agent
- license
- ELv2
- metadata.author
- gaai-framework
- metadata.version
- 1.0
- metadata.category
- cross
- metadata.track
- cross-cutting
- metadata.id
- SKILL-PROJECT-SURFACE-SCAN-001
- metadata.updated_at
- 2026-04-29
- metadata.status
- stable
- inputs
- project_root_path
- outputs
- surface_scan_result
Files
Just SKILL.md in .gaai/core/skills/cross/project-surface-scan of digipulse-engineering/GAAI-framework.
Open the folder on GitHubat commit a26ea7a
Compare with similar skills
Project Surface Scan 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 |
|---|---|---|---|---|---|---|
| Project Surface Scan this skilldigipulse-engineering/GAAI-framework | 163 | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 8 repos | ~4.3k | Automated safety check: Pass | None | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| Kubeshark KFL2 Filter Referencekubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Kubernetes Network Root Cause Analysiskubeshark/kubeshark | 12k | — | ~5.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Kubeshark KFL2 Filter Reference
kubeshark/kubeshark
Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
Kubernetes Network Root Cause Analysis
kubeshark/kubeshark
Investigates past Kubernetes incidents from Kubeshark traffic snapshots: takes captures, dissects API calls, extracts PCAPs and compares traffic over time.
Caveman Gateway Setup
JuliusBrussee/caveman
Routes every LLM call in a repository through the Caveman Cloud gateway in record mode, so requests and costs are measured without changing behavior.
More from digipulse-engineering/GAAI-framework
All 55 skills in this repoEval Run
digipulse-engineering/GAAI-framework
Evaluate any output file against a structured evals.yaml assertions file and produce a score report with per-assertion pass/fail results.
Pattern Transfer
digipulse-engineering/GAAI-framework
Discover structurally similar patterns across domains, assess transfer viability via structural invariant checking, and propose domain adaptations with risk gates.
Skill Optimize
digipulse-engineering/GAAI-framework
Run a structured evaluate-analyze-improve cycle on any GAAI skill to measure quality, detect regressions, and propose targeted improvements.
Abort Safe Handler
digipulse-engineering/GAAI-framework
Orchestrator-level Stage 4 entry gate for /gaai:bootstrap. An agent skill from digipulse-engineering/GAAI-framework.
Create Skill
digipulse-engineering/GAAI-framework
Guide creation of a new GAAI skill following the agentskills.io spec and GAAI best practices.
Discovery High Level Plan
digipulse-engineering/GAAI-framework
Transform vague or high-level human intent into a governed Discovery action plan.
Related
Categories
Questions about Project Surface Scan
What does Project Surface Scan do?
Scan project root for file tree, dominant languages, and LOC estimate. Project Surface Scan is an agent skill from digipulse-engineering/GAAI-framework. Scan project root for file tree, dominant languages, and LOC estimate.
When should I use Project Surface Scan?
Project Surface Scan fits situations like: tasks that involve Observability.
How do I install Project Surface Scan in Claude Code?
Run `npx skills add digipulse-engineering/GAAI-framework --skill project-surface-scan -a claude-code`. Or copy the skill folder (.gaai/core/skills/cross/project-surface-scan in digipulse-engineering/GAAI-framework) into .claude/skills/project-surface-scan in your project. Claude Code loads it when a task matches its description.
How do I install Project Surface Scan in Codex?
Run `npx skills add digipulse-engineering/GAAI-framework --skill project-surface-scan -a codex`. Or copy the skill folder (.gaai/core/skills/cross/project-surface-scan in digipulse-engineering/GAAI-framework) into .agents/skills/project-surface-scan in your project. Codex loads it when a task matches its description.
Can I use Project Surface Scan 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 digipulse-engineering/GAAI-framework --skill project-surface-scan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/project-surface-scan, .gemini/skills/project-surface-scan, .github/skills/project-surface-scan and .opencode/skills/project-surface-scan in your project.
What does Project Surface Scan need to run?
SKILL.md names no scripts, command-line tools or credentials: Project Surface Scan is instructions for the agent only. Our summary lists: Python 3. Compatibility (from SKILL.md): Works with any filesystem-based AI coding agent.
Does Project Surface Scan access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Project Surface Scan 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 Project Surface Scan use?
Project Surface Scan has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Project Surface Scan use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Project Surface Scan?
Skills that share tags, products or a category with Project Surface Scan: Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars), Kubeshark Installer (kubeshark/kubeshark, 12k stars), Kubeshark KFL2 Filter Reference (kubeshark/kubeshark, 12k stars) and KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Project Surface Scan?
digipulse-engineering (a GitHub organization) maintains it in digipulse-engineering/GAAI-framework, which has 163 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on September 29, 2026.
Source: digipulse-engineering/GAAI-framework on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.