Agent skill

gsd:intel

Query, inspect, or refresh codebase intelligence files in .planning/intel/

Dave Poon3,251★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add davepoon/buildwithclaude --skill intel --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Allowed tools: -Read-Bash-Task
Path: plugins/gsd/skills/intel/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 3,251
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

**STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's command system. Using the Read tool on this file wastes tokens. Begin executing Step 0 immediately.** ## Step 0 -- Banner **Before ANY tool calls**, display this banner: ``` GSD > INTEL ``` Then proceed to Step 1. ## Step 1 -- Config Gate Check if intel is enabled by reading `.p

More from buildwithclaude
All skills →
About this skill
What does the gsd:intel skill do?

Query, inspect, or refresh codebase intelligence files in .planning/intel/

How do I install it?

Run `npx skills add davepoon/buildwithclaude --skill intel --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From davepoon/buildwithclaude, a repository with 3,251 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going