mirror of
https://github.com/superdesigndev/treg.git
synced 2026-10-02 03:24:35 +08:00
Jason ZhouandClaude Opus 5.5
ce916f288d
* feat(web): /intent-signals landing page for the buyer-signals launch "Claude monitor buyer signals": built from /people-search, keeping its skill grid (now eight signal tiles from the launch film's real run) and the People Search Bench. New: a morning-run demo, a three-step 'your agent is the monitor' section (Claude Code /schedule, Codex from cron, diff against the last list), the $0.98 four-source receipt, and pay-per-check pricing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(web): /intent-signals scenes from the launch film Replace the monitor steps, the receipt table and the signal tile grid with the film's own scenes, rebuilt as HTML: a radar and signal feed that judges each post, a thread → scored companies → decision makers flow with vendor waterfall, 'treg monitors…' with evidence cards per signal, and the daily hot-leads list a scheduled run grows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(web): /intent-signals hero plays the whole film in one take The hero now runs monitor the topic → read the thread → score companies → find decision makers as one continuous, clickable demo, replacing the old hero table and the two separate scene sections. The 'treg monitors…' section goes back to the skill tile grid, each tile now a small visual scene (post, new position, news, job postings, funding, headcount chart, tech adopters, Reddit thread) instead of text rows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(web): /intent-signals headline 'Claude for Signal Monitor' and the real Reddit mark Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * style(web): /intent-signals nav drops the Signals and Daily list links Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(web): /intent-signals works at every width Tablet keeps every column and a smaller radar beside the feed; phone puts the radar above the feed and the post above its thread, folds secondary columns, wraps the prompt bar and truncates names instead of overlapping. The prompt cursor now honours [hidden], and a new prompt clears the last reply before it types. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * style(web): /intent-signals headline 'Claude for Monitor Leads Signal' in Geist Pixel Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * fix(web): /intent-signals prices from the billed run, not the film's $0.98 The launch run's LinkedIn, Reddit and X sweep billed $0.52 for 2,945 signals (4,710 with the free GitHub stargazers): $0.0002 per signal checked. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(skills): lead-signals, the /intent-signals workflow as a skill Detect, qualify, contact, hand back a ranked list; optionally keep watching on the agent's own schedule with a diff against the last list. It names signal families and the words to search the catalog with, never endpoint ids, so it stays right as the catalog grows. Served at /skills/lead-signals/SKILL.md and as the third entry in the well-known skills index, like make-ugc. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(skills): lead-signals description says only when to use it; example vendors per signal Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(skills): install our skills with npx skills add superdesigndev/treg The skills CLI (skills.sh) reads skills/ and skips symlinks, so build_plugin.py now also writes real copies of the workflow skills (make-ugc, lead-signals) there, and --check keeps them in step with src/treg/web/skills. The six skills that are repo tooling carry metadata.internal so the CLI hides them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore(skills): vendor-listing is repo tooling, hidden from npx skills add Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(web): /intent-signals shows the one-line skill install npx skills add superdesigndev/treg --skill lead-signals, beside the treg set-up command; both copy buttons share one handler and wrap on a phone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(cli): treg skill bootstrap installs every public skill the registry advertises install.sh already runs it; it now also installs each skill in /.well-known/skills/index.json (make-ugc, lead-signals) into the same global agent folders as the treg skill. Best-effort, and a name from the index must be a plain slug before it becomes a directory. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(skills): lead-signals sends an agent without treg to llms.txt to set up Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * feat(web): the buyer-signals page lives at /leads-signals Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * style(web): /leads-signals tools grid shows Aviato people search instead of Apollo Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * style(web): /leads-signals nav reads Leads signals Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * refactor(web): /leads-signals served by _static_page like the other launch pages The catalog's size comes from {ENDPOINTS}/{PROVIDERS} instead of typed numbers, and the page carries the shared share image. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs(context): the installer also installs the advertised workflow skills Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
5.1 KiB
5.1 KiB
name, description
| name | description |
|---|---|
| lead-signals | 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
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.
Runs on treg. If it isn't set up (treg --version fails), read https://treg.to/llms.txt and follow it to
install and sign in, then come back here.
The run
- Detect raw signals for the user's buyer.
- Qualify. Drop the noise; most runs discard more than half. A signal list is not a lead list.
- Contact. Company → decision maker → work email, only for rows that survived.
- Hand back a ranked list: person, company, the signal, why now in one line, source link, email if found. State coverage plainly: "1,180 engaged, 800 emails found".
Default for "find buyers for X" or "monitor Y": search posts about the pain on LinkedIn, X and Reddit → read the comments and reactions on the best posts → keep people whose title fits → roll them up by company and score → decision makers and emails at the top companies.
Signals
The vendors are examples of who answers today, not a list to stick to: search, and take whatever the catalog ranks best now.
| Signal | Search the catalog for | Example vendors | Keep | Drop |
|---|---|---|---|---|
| Posts and complaints | "search linkedin posts", "search reddit posts", "search x posts" | HarvestAPI, AnyAPI, ScrapeCreators | first-person pain, last 7 days, names you or a competitor | vendors, recruiters, consultants selling to the same crowd |
| Post engagers | "linkedin post comments", "post reactions" | HarvestAPI, Fetchin | commented beats reacted; title fits | the author's colleagues, "great post" |
| Reviews | "google reviews" | Serper, AnyAPI | low stars about the job you do | reviews older than a quarter |
| Hiring | "job postings" | HarvestAPI, PredictLeads, Apollo | a role that implies your product, last 30 days, several roles | staffing firms, evergreen reposts |
| Job change | "job change" | Datagma, LeadMagic | moved in the last 90 days into a company that fits; a former user | moves inside the same group |
| Funding | "funding rounds" | PredictLeads, Aviato | last 90 days, stage fits your price | debt read as growth |
| Tech adoption | "technology users", "tech stack" | PredictLeads, Tomba | a tool added or removed recently: a competitor or an integration | tags every site has |
| Headcount | "headcount", "workforce" | CompanyEnrich, Akta | direction and rate in your buyer's team | jumps from an acquisition |
| News | "company news" | PredictLeads, Akta | launch, acquisition, exec hire, last 30 days | syndicated duplicates |
| Ads | "ads library" | Meta Ad Library, Adyntel | live campaigns: budget and an offer to position against |
Anything else is a composition. A page change: scrape the page, keep a hash, compare next run. Custom
intent: a Google search such as "migrating from <competitor>". Repo stars: GitHub with the team's own
token.
Finding the endpoint
The catalog changes every week, so never trust a remembered endpoint id.
treg catalog search "<the job in plain words>", not a vendor name.- Prefer a routed
treg.*endpoint when there is one: the team's own keys first, then providers in order, and most misses are free. treg catalog get <id>: the price, the hit rate (it found something), not just works (it returned 200), and the row's note.- One small call first. Read the reported charge and
_treg.served_by, then scale. - Nothing fits:
treg catalog request "<what is missing>".
For emails use the routed finder, treg.people.email.find, and always send
X-Treg-Route-Max-Cost: 0.05; uncapped, a miss can walk up to the dearest provider.
Score
Fit first (no fit, no row), then timing (fresher wins), then strength (two independent signals on one account beat one). Every row carries its reason in the user's words.
Keep watching
When the user wants it recurring:
- Run once and report what it cost (sum the reported charges): that is the price of each run.
- Keep
signals.csvkeyed by person URL, signal and source URL. Later runs report only new keys. The first run is the baseline; say so. - Schedule it with the user's agent: Claude Code
/schedule(a cloud routine) or/loop(while the session is open), Codexcodex exec "<prompt>"from cron, any other agent its own scheduler. The scheduled run needsTREG_TOKEN(an agent token fromtreg org agent-new) and a place forsignals.csvit can read and write, such as a repo file or a sheet.
Before the first list
Say once: outreach to EU and UK people needs a lawful basis, and suppression and unsubscribe lists come first. Then hand over the list; the user decides how to use it.