Geo Fundamentals
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
A skill your agent uses when the user wants to find buyers, warm or hot leads, or in-market accounts; asks about buying signals, intent signals or trigger events; wants to know who is complaining…
$ npx skills add superdesigndev/treg --skill lead-signals -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install superdesigndev/treg lead-signals --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/superdesigndev/treg.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/lead-signals .claude/skills/lead-signals && 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 "lead-signals" agent skill from https://github.com/superdesigndev/treg/tree/main/skills/lead-signals into .claude/skills/lead-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-signals", 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/superdesigndev/treg/tree/main/skills/lead-signalsType 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 superdesigndev/treg --skill lead-signals -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install superdesigndev/treg lead-signals --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superdesigndev/treg.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/lead-signals .agents/skills/lead-signals && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lead-signals" agent skill from https://github.com/superdesigndev/treg/tree/main/skills/lead-signals into .agents/skills/lead-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-signals", 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 superdesigndev/treg --skill lead-signals -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install superdesigndev/treg lead-signals --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superdesigndev/treg.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/lead-signals .cursor/skills/lead-signals && 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 "lead-signals" agent skill from https://github.com/superdesigndev/treg/tree/main/skills/lead-signals into .cursor/skills/lead-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-signals", 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/superdesigndev/treg.git --path skills/lead-signals--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 superdesigndev/treg --skill lead-signals -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install superdesigndev/treg lead-signals --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superdesigndev/treg.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/lead-signals .gemini/skills/lead-signals && 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 "lead-signals" agent skill from https://github.com/superdesigndev/treg/tree/main/skills/lead-signals into .gemini/skills/lead-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-signals", 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 superdesigndev/treg lead-signalsInstalls 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 superdesigndev/treg --skill lead-signals -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/superdesigndev/treg.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/lead-signals .github/skills/lead-signals && 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 "lead-signals" agent skill from https://github.com/superdesigndev/treg/tree/main/skills/lead-signals into .github/skills/lead-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-signals", 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 superdesigndev/treg --skill lead-signals -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install superdesigndev/treg lead-signals --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superdesigndev/treg.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/lead-signals .opencode/skills/lead-signals && 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 "lead-signals" agent skill from https://github.com/superdesigndev/treg/tree/main/skills/lead-signals into .opencode/skills/lead-signals/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lead-signals", 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.
lead-signalsA skill your agent uses when the user wants to find buyers, warm or hot leads, or in-market accounts; asks about buying signals, intent signals or trigger events; wants to know who is complaining…
Lead Signals is an agent skill from superdesigndev/treg. Use when the user wants to find buyers, warm or hot leads, or in-market accounts; asks about buying signals, intent signals or trigger events; wants to know who is complaining about a problem, engaging with a post, hiring for a role, changing jobs, raising money or adopting a tool; or wants to monitor a topic, a competitor or a list of accounts for people ready to buy.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Marketing & SEO. The repository describes itself as: OpenRouter for agent tools. Join community here: https://discord.gg/6mQYYfFMAn.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 77ae02e. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
codexFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
treg.toFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
TREG_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Lead Signals loads about 1.3k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 741 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.
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.
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 741 words (~1,293 tokens).
“A signal is a public fact that makes a conversation timely: someone complained about the problem you solve, engaged with a post about it, hired for it, raised money, switched tools.”
Just SKILL.md in skills/lead-signals of superdesigndev/treg.
Open the folder on GitHubat commit 77ae02e
Lead Signals 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 |
|---|---|---|---|---|---|---|
| Lead Signals this skillsuperdesigndev/treg | 4.8k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Geo Fundamentalswasp-lang/wasp | 19k | 9 repos | ~861 | Automated safety check: Pass | MIT | |
| Ab Testingcoreyhaines31/marketingskills | 54k | 3 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Hreflang and International SEOAgriciDaniel/claude-seo | 18k | 5 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Referralscoreyhaines31/marketingskills | 54k | 2 repos | ~2.4k | Automated safety check: Pass | MIT | |
| SEO GeoReScienceLab/opc-skills | 1.8k | 4 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 |
wasp-lang/wasp
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.
AgriciDaniel/claude-seo
Audits, validates and generates hreflang tags for multi-language and multi-region sites in HTML, HTTP headers or XML sitemaps, flagging common code and return-tag mistakes.
coreyhaines31/marketingskills
When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.
ReScienceLab/opc-skills
SEO & GEO (Generative Engine Optimization) for websites. An agent skill from ReScienceLab/opc-skills.
LeoYeAI/openclaw-marketing-skills
When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform.
superdesigndev/treg
Add a provider to treg's OAuth registry (the ones treg holds its own approved app for).
superdesigndev/treg
One-command local dev stack for tools-registry. An agent skill from superdesigndev/treg.
superdesigndev/treg
Traps when running Google Ads through treg — the API requirements and cleanup semantics that cost round-trips or money.
superdesigndev/treg
Traps to avoid when querying Google Analytics 4 through treg — cases where the GA4 Data API returns a confident wrong answer instead of an error.
superdesigndev/treg
Traps to avoid when querying Google Search Console through treg — cases where the API returns a confident wrong answer instead of an error, especially around totals and recent-date trends.
superdesigndev/treg
A skill your agent uses when the user wants Claude Code to remember their preferences across sessions, asks for a memory mod or memory harness for Claude Code, mentions the Jev memory classifier or…
Categories
A skill your agent uses when the user wants to find buyers, warm or hot leads, or in-market accounts; asks about buying signals, intent signals or trigger events; wants to know who is complaining…. Lead Signals is an agent skill from superdesigndev/treg. Use when the user wants to find buyers, warm or hot leads, or in-market accounts; asks about buying signals, intent signals or trigger events; wants to know who is complaining about a problem, engaging with a post, hiring for a role, changing jobs, raising money or adopting a tool; or wants to monitor a topic, a competitor or a list of accounts for people ready to buy.
Lead Signals fits situations like: the user wants to find buyers; in-market accounts; asks about buying signals; wants to know who is complaining about a problem.
Run `npx skills add superdesigndev/treg --skill lead-signals -a claude-code`. Or copy the skill folder (skills/lead-signals in superdesigndev/treg) into .claude/skills/lead-signals in your project. Claude Code loads it when a task matches its description.
Run `npx skills add superdesigndev/treg --skill lead-signals -a codex`. Or copy the skill folder (skills/lead-signals in superdesigndev/treg) into .agents/skills/lead-signals in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add superdesigndev/treg --skill lead-signals -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lead-signals, .gemini/skills/lead-signals, .github/skills/lead-signals and .opencode/skills/lead-signals in your project.
Going by SKILL.md and its folder, Lead Signals needs the command-line tools its instructions call (codex) and credentials named TREG_TOKEN. Our summary lists: A credential in TREG_TOKEN.
SKILL.md names 1 domain. As links in the text: treg.to. This is read from the text; nothing was executed.
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.
Lead Signals has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Lead Signals: Geo Fundamentals (wasp-lang/wasp, 19k stars), Ab Testing (coreyhaines31/marketingskills, 54k stars), Hreflang and International SEO (AgriciDaniel/claude-seo, 18k stars) and Referrals (coreyhaines31/marketingskills, 54k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
superdesigndev (a GitHub organization) maintains it in superdesigndev/treg, which has 4,763 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 8, 2026.
Source: superdesigndev/treg on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.