github-lead-qualification

A GitHub lead-qualification procedure for deciding whether potential organizations fit a product's target customer profile. It uses existing Airtable records and evidence to assign a fit category.

In plain words
What is it for?
Reviewing existing GitHub lead candidates, marking them as a fit, possible fit, or not a fit, and updating their priority, status, evidence, and next action.
Why use it?
It prevents unsuitable prospects from moving into outreach and keeps qualification decisions traceable. It also assigns the next step for each candidate.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/ducksss/codex-profiles/github-lead-qualification
Any agent
npx skills add Ducksss/codex-profiles --skill github-lead-qualification
Clone the repo
git clone --depth 1 https://github.com/Ducksss/codex-profiles

Made for: Claude Code, Codex.

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,164 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.01164
Opus 5 $0.00021 $0.00582
Sonnet 5 $0.00008 $0.00233
Haiku 4.5 $0.00004 $0.00116

Measured 2d ago against content hash 66df6960b31b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-lead-qualification scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/github-lead-qualification/SKILL.md · 106 lines

How it starts

The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub Lead Qualification

Purpose

Decide whether GitHub lead-gen candidates are real fits for codex-profiles, then update Airtable with evidence and a next phase. This skill consumes Airtable targets whose Next Action = Run lead qualification.

Required Context

Read README.md for current product positioning, LAUNCH.md for policy gates, and the selected Airtable target for live outreach state. Load references/icp-rules.md before scoring.

Boundaries

  • Update Airtable Targets and append Log entries only.
  • Consume Airtable targets whose Next Action = Run lead qualification.
  • Use Log.Workflow = lead-qualification for every meaningful decision.
  • Assign exactly one of ICP: yes, ICP: maybe, or ICP: no.
  • Set Priority, Status, Last Checked, Next Action, and evidence.
  • Do not discover new leads.
  • Do not draft PRs, issues, comments, emails, DMs, forum posts, listing submissions, or maintainer replies.
  • Do not contact externally.

Accepted Input

  • Consume only Backlog or Deferred targets whose Next Action = Run lead qualification.
  • Leave ready ICP: yes targets as Backlog with Next Action = Run closing draft; leave all other outcomes with a concrete recheck, blocker, or terminal next action.
  • Issue-first is a valid closing-draft route when the target is a truthful fit, requires an issue before a PR, and has no existing submission.

Tracker Protocol

Create a unique run-<UTC-timestamp>-<random-suffix> <run-id>, list candidate rows, and inspect each selected row before claiming it:

node scripts/outreach-tracker.mjs list --json
node scripts/outreach-tracker.mjs list --status Backlog --json
node scripts/outreach-tracker.mjs list --status Deferred --json
node scripts/outreach-tracker.mjs get <key> --json
node scripts/outreach-tracker.mjs claim <key> --by <run-id>

If claim exits 3, skip the target without writing or contacting externally. After a successful claim, use a shell trap or equivalent finally cleanup to release on every exit path, including partial persistence or logging failure. After qualification, persist the decision and stable phase log:

Read the full file on GitHub · 106 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 106 lines · 42 tokens per session scan A 66df6960b31b

Subscribe to this mod's changes

github-lead-qualification is a skill published in the GitHub repository Ducksss/codex-profiles (108 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 1,164 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

claude-api

Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements). TRIGGER when: code imports anthropic/@anthropic-ai/sdk; user asks for…

warpdotdev/warp · 193 tokens

gmail

Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.

vellum-ai/vellum-assistant · 20 tokens

gui-onboarding-verification-skill

GUI desktop app only. Launch two parallel Oz cloud agents with computer use to download and install the latest stable Linux Warp build, capture screenshots while walking through first-time onboarding in both logged-out and logged-in states, then selectively fan out follow-up cloud agents for distinct onboarding…

warpdotdev/warp · 98 tokens

create-skill

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

warpdotdev/warp · 64 tokens

app-builder

Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use…

vellum-ai/vellum-assistant · 162 tokens

contacts

Manage contacts, communication channels, access control, and invite links.

vellum-ai/vellum-assistant · 14 tokens