Ops Leadgen
Lifecycle-Innovations-Limited/claude-ops
OPS on-demand: This skill should be used when the user asks to "leadgen drafts", "cold email approve"…
Reverse-engineer a company's sales and marketing tech stack from public signals.
Install Tech Stack Teardown
$ npx skills add majiayu000/claude-skill-registry --skill tech-stack-teardown -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install majiayu000/claude-skill-registry tech-stack-teardown --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/majiayu000/claude-skill-registry.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/analysis/tech-stack-teardown .claude/skills/tech-stack-teardown && 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 "tech-stack-teardown" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/tech-stack-teardown into .claude/skills/tech-stack-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-stack-teardown", 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/majiayu000/claude-skill-registry/tree/main/skills/analysis/tech-stack-teardownType 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 majiayu000/claude-skill-registry --skill tech-stack-teardown -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install majiayu000/claude-skill-registry tech-stack-teardown --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/analysis/tech-stack-teardown .agents/skills/tech-stack-teardown && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tech-stack-teardown" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/tech-stack-teardown into .agents/skills/tech-stack-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-stack-teardown", 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 majiayu000/claude-skill-registry --skill tech-stack-teardown -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install majiayu000/claude-skill-registry tech-stack-teardown --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/analysis/tech-stack-teardown .cursor/skills/tech-stack-teardown && 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 "tech-stack-teardown" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/tech-stack-teardown into .cursor/skills/tech-stack-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-stack-teardown", 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/majiayu000/claude-skill-registry.git --path skills/analysis/tech-stack-teardown--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 majiayu000/claude-skill-registry --skill tech-stack-teardown -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install majiayu000/claude-skill-registry tech-stack-teardown --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/analysis/tech-stack-teardown .gemini/skills/tech-stack-teardown && 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 "tech-stack-teardown" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/tech-stack-teardown into .gemini/skills/tech-stack-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-stack-teardown", 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 majiayu000/claude-skill-registry tech-stack-teardownInstalls 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 majiayu000/claude-skill-registry --skill tech-stack-teardown -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/analysis/tech-stack-teardown .github/skills/tech-stack-teardown && 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 "tech-stack-teardown" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/tech-stack-teardown into .github/skills/tech-stack-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-stack-teardown", 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 majiayu000/claude-skill-registry --skill tech-stack-teardown -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install majiayu000/claude-skill-registry tech-stack-teardown --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/majiayu000/claude-skill-registry.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/analysis/tech-stack-teardown .opencode/skills/tech-stack-teardown && 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 "tech-stack-teardown" agent skill from https://github.com/majiayu000/claude-skill-registry/tree/main/skills/analysis/tech-stack-teardown into .opencode/skills/tech-stack-teardown/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tech-stack-teardown", 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
tech-stack-teardown- GitHub stars
- 666
- Used in
- 2 other repos
- Token cost
- ~3.1k tokens
- SKILL.md length
- 1,126 words
- Files
- 2
- Skills in repo
- 1,273
- Repo updated
- First seen
- Licence
- MIT
At a glance
Reverse-engineer a company's sales and marketing tech stack from public signals.
- Works in 2 steps: Required → Optional (for Apify Technology Profiler)
- Tasks that involve Web scraping
- SKILL.md covers What It Detects, How It Works, Cost and Setup, plus 6 more sections
- Calls python3, pip3 and curl; reaches console.apify.com; needs APIFY_API_TOKEN
What it does
Tech Stack Teardown is an agent skill from majiayu000/claude-skill-registry. Reverse-engineer a company's sales and marketing tech stack from public signals. Detects CRMs, cold email tools, people databases, ad pixels, email delivery services, and outbound sending domains via DNS records, website source inspection, Apify technology profiling, blacklist checks, and public spam complaint searches. Works on single companies or batches. Outputs a structured markdown report per company.
Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `metadata.json`).
It sits in Sales & Support, covering Web scraping, Transactional email and Cold outreach. It works with Apify and SendGrid. The repository describes itself as: Searchable Claude Code skills catalog with source-linked guides and generated registry artifacts. The licence is MIT.
When your agent uses it
- Tasks that involve Web scraping
- Tasks that involve Transactional email
- Tasks that involve Cold outreach
Example prompts
- “/tech-stack-teardown”
Requirements
- Python 3
- A credential in APIFY_API_TOKEN
Workflow steps
2 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 2d14a69. 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
Shell commands in SKILL.md call:
python3pip3curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
console.apify.com
Also links to:
apify.commxtoolbox.comcheck.spamhaus.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
APIFY_API_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Tech Stack Teardown loads about 3.1k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 1,126 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:112
# Add to .env:
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
The full file from majiayu000/claude-skill-registry at commit 2d14a69, republished under its MIT licence (© majiayu000). 1,126 words, ~3,068 tokens.
Download SKILL.mdSave it as
.claude/skills/tech-stack-teardown/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- tech-stack-teardown
- description
- Reverse-engineer a company's sales and marketing tech stack from public signals. Detects CRMs, cold email tools, people databases, ad pixels, email delivery services, and outbound sending domains via DNS records, website source inspection, Apify technology profiling, blacklist checks, and public spam complaint searches. Works on single companies or batches. Outputs a structured markdown report per company.
- tags
- competitive-intel
Tech Stack Recon
Reverse-engineer a company's sales, marketing, and outbound infrastructure from public signals. No login, no API access to their tools needed — everything is derived from DNS records, website source code, technology profiling, blacklist databases, and public complaints.
What It Detects
| Category | Tools Detected |
|---|---|
| CRM | HubSpot, Salesforce (via SPF, website pixels, DNS) |
| Cold Email Tools | Smartlead, Instantly, Outreach, Salesloft, Lemlist (via SPF, DKIM, TXT records, website source) |
| People Databases | Apollo, ZoomInfo, Clearbit, 6sense (via website tracker scripts) |
| Email Delivery | SendGrid, Amazon SES, Postmark, Mailgun, Mandrill (via SPF includes, DKIM selectors) |
| Email Marketing | Mailchimp, Brevo, ActiveCampaign, Klaviyo (via DKIM selectors) |
| Ad Retargeting | LinkedIn Insight Tag, Facebook Pixel, AdRoll, Reddit Ads, Twitter Ads (via Apify profiler + source) |
| Website Builder | Webflow, Framer, Next.js, WordPress (via Apify profiler + source) |
| Chat / Support | Intercom, Drift, Crisp, Zendesk (via website source) |
| Analytics | Google Analytics, Segment, Mixpanel, Amplitude, PostHog, Heap (via website source) |
| Outbound Domains | Separate cold sending domains (via SPF-only Google Workspace + redirect to primary) |
How It Works
The skill runs 5 layers of detection, each revealing different signals:
Layer 1: DNS Records (Free, instant)
MX → Primary email provider (Google Workspace, Microsoft 365, etc.)
SPF → Every service authorized to send email on their behalf
DKIM → Cryptographic proof of which tools actually send email
DMARC → Email authentication policy (how strict they are)
TXT → Misc verifications (Smartlead tracking domains, tool verifications)
CNAME → Subdomains pointing to third-party servicesThis is the highest-signal layer. SPF and DKIM don't lie — if SendGrid is in their SPF, they use SendGrid.
Layer 2: Website Source Inspection (Free, instant)
Fetches the target website and searches HTML for:
- Tracking pixels (Apollo, REB2B, HubSpot, Facebook, LinkedIn)
- Script tags loading third-party tools
- Meta tags and framework signatures
- Hidden form handlers and API endpoints
Layer 3: Apify Technology Profiler (Pay-per-use, ~$0.005/domain)
Runs justa/technology-profiling-engine actor for deep detection of 7,000+ technologies using 8-tier inspection with confidence scores. Catches tools that don't appear in source code (loaded dynamically, via GTM, etc.).
Layer 4: Blacklist Checks (Free, instant)
Queries 6 major DNS-based blacklists:
- Spamhaus (zen.spamhaus.org)
- Barracuda (b.barracudacentral.org)
- SpamCop (bl.spamcop.net)
- SORBS (dnsbl.sorbs.net)
- SURBL (multi.surbl.org)
- URIBL (black.uribl.com)
Layer 5: Public Complaint Search (Free)
Web searches for spam complaints on Trustpilot, Reddit, SpamCop forums, and general web. Also searches for the company + tool names to find public mentions of their stack.
Cost
| Component | Cost |
|---|---|
| DNS queries | Free |
| Website source fetch | Free |
| Blacklist checks | Free |
| Web searches | Free |
| Apify Technology Profiler | ~$0.005 per domain |
Typical costs:
| Scenario | Domains | Est. Cost |
|---|---|---|
| Single company | 1 | ~$0.005 |
| Small batch | 5 | ~$0.025 |
| Large batch | 20 | ~$0.10 |
Skip the Apify profiler with --no-apify for free-only analysis (DNS + source + blacklists).
Setup
1. Required
# dig (DNS lookups) — included on macOS/Linux
which dig
# curl (website source fetch) — included on macOS/Linux
which curl
# Python 3 with requests + dotenv
pip3 install requests python-dotenv2. Optional (for Apify Technology Profiler)
# Get your token at https://console.apify.com/account/integrations
# Add to .env:
APIFY_API_TOKEN=apify_api_YOUR_TOKEN_HEREUsage
Single Company
python3 scripts/recon.py --domains pump.coBatch of Companies
python3 scripts/recon.py --domains "dili.ai,pump.co,runautomat.com"Free-Only Mode (No Apify)
python3 scripts/recon.py --domains pump.co --no-apifyOutput to File
python3 scripts/recon.py --domains "dili.ai,pump.co" --output /path/to/report.mdJSON Output
python3 scripts/recon.py --domains pump.co --jsonWhat the Script Does
For each domain:
- DNS Scan — Queries MX, SPF, DKIM (18 common selectors), DMARC, TXT records, and 30+ common subdomains (email, tracking, click, bounce, send, smtp, mail, etc.)
- Website Source Scan — Fetches the homepage HTML and greps for 40+ known tool signatures (script URLs, pixel IDs, tracking domains)
- Apify Technology Profile (optional) — Runs deep 8-tier technology detection for 7,000+ technologies with confidence scores
- Blacklist Check — Queries 6 DNS-based blacklists for the domain
- Outbound Domain Detection — Checks if common variations of the domain exist (get[name].com, try[name].com, [name]reach.com, etc.) and analyzes their DNS for cold outbound patterns
- Report Generation — Produces a structured markdown report with confirmed tools, evidence, email auth assessment, blacklist status, and an overall assessment
Agent Integration
When using this skill as an agent, follow this flow:
- User provides one or more company domains
- Run
recon.pyfor all domains (confirm Apify cost if > 5 domains) - Present the report — group findings by:
- Confirmed tools (with evidence)
- Email authentication (SPF/DKIM/DMARC assessment)
- Deliverability (blacklist status + spam complaints)
- Notable signals (outbound domains, missing DMARC, SPF gaps)
- If batch, include a comparative summary table at the end
Agent Without the Script
The agent can perform all checks manually using built-in tools:
DNS checks — Use Bash tool:
dig +short MX example.com
dig +short TXT example.com
dig +short TXT _dmarc.example.com
dig +short TXT selector._domainkey.example.com
dig +short CNAME subdomain.example.comWebsite source scan — Use Bash tool:
curl -sL https://www.example.com | grep -oi 'pattern1\|pattern2\|pattern3' | sort -uBlacklist checks — Use Bash tool:
dig +short example.com.zen.spamhaus.org AApify profiler — Use Bash tool with Python:
# See scripts/recon.py for the full implementationSpam complaints — Use WebSearch tool:
"example.com" spam OR unsolicited OR "cold email" OR blacklistDNS Record Cheat Sheet
SPF Includes → Tool Identification
| SPF Include | Tool |
|---|---|
_spf.google.com | Google Workspace |
spf.protection.outlook.com | Microsoft 365 |
sendgrid.net | SendGrid |
amazonses.com | Amazon SES |
*.hubspotemail.net | HubSpot |
*.rsgsv.net or servers.mcsv.net | Mailchimp/Mandrill |
spf.mandrillapp.com | Mandrill (Mailchimp transactional) |
mail.zendesk.com | Zendesk |
*.freshdesk.com | Freshdesk |
spf.mailjet.com | Mailjet |
spf.brevo.com | Brevo (Sendinblue) |
_spf.salesforce.com | Salesforce |
mktomail.com | Marketo |
postmarkapp.com | Postmark |
mailgun.org | Mailgun |
Show full SKILL.md (437 more words)Show less
DKIM Selectors → Tool Identification
| Selector Pattern | Tool |
|---|---|
google._domainkey | Google Workspace |
selector1._domainkey / selector2._domainkey | Microsoft 365 |
s1._domainkey / s2._domainkey → *.sendgrid.net | SendGrid |
k1._domainkey → *.mcsv.net or dkim.mcsv.net | Mailchimp |
k2._domainkey / k3._domainkey → dkim2.mcsv.net / dkim3.mcsv.net | Mailchimp |
mandrill._domainkey | Mandrill |
pm._domainkey | Postmark |
smtp._domainkey | Generic SMTP |
em._domainkey | Various (check CNAME target) |
TXT Records → Tool Identification
| TXT Pattern | Tool |
|---|---|
open.sleadtrack.com | Smartlead (custom tracking domain) |
hubspot-developer-verification=* | HubSpot |
anthropic-domain-verification-* | Anthropic (Claude) |
MS=* | Microsoft 365 |
google-site-verification=* | Google Search Console |
slack-domain-verification=* | Slack |
atlassian-domain-verification=* | Atlassian (Jira/Confluence) |
docusign=* | DocuSign |
facebook-domain-verification=* | Facebook/Meta |
_github-pages-challenge-* | GitHub Pages |
stripe-verification=* | Stripe |
Website Source Patterns → Tool Identification
| Pattern in HTML | Tool |
|---|---|
assets.apollo.io/micro/website-tracker | Apollo.io (visitor tracking) |
hs-script or js.hs-scripts.com | HubSpot |
px.ads.linkedin.com | LinkedIn Insight Tag |
connect.facebook.net or fbq( | Facebook Pixel |
snap.licdn.com | LinkedIn Insight Tag |
cdn.segment.com | Segment |
cdn.mxpnl.com or mixpanel | Mixpanel |
cdn.amplitude.com | Amplitude |
app.posthog.com or posthog | PostHog |
widget.intercom.io | Intercom |
js.driftt.com | Drift |
client.crisp.chat | Crisp |
static.zdassets.com | Zendesk |
s3-us-west-2.amazonaws.com + reb2b | REB2B |
clearbit.com/tag.js or reveal | Clearbit Reveal |
6sc.co or 6sense | 6sense |
tag.demandbase.com | Demandbase |
d.adroll.com | AdRoll |
googletagmanager.com | Google Tag Manager |
gtag('config', 'G-*') | Google Analytics 4 |
Cold Outbound Domain Patterns
A separate domain is being used for cold email if it has:
- Google Workspace MX (or similar) but no product/marketing email tools in SPF
- SPF that only includes
_spf.google.com(sending from raw mailboxes) - A 301/302 redirect to the company's primary domain
- No website content of its own
- Domain name follows patterns like:
[brand]reach.com,get[brand].com,try[brand].com,meet[brand].com,[brand]hq.com
DMARC Assessment Guide
| Policy | Meaning | Assessment |
|---|---|---|
p=reject | Reject unauthenticated email | Strong — best practice |
p=quarantine | Send to spam if unauthenticated | Good — enforcing |
p=none | Monitor only, don't enforce | Weak — anyone can spoof the domain |
| No DMARC record | No policy at all | Missing — wide open to spoofing |
Troubleshooting
"No tools detected"
- The company may be very early-stage with minimal tooling
- Some tools (like Apollo used only for prospecting, not sending) leave no DNS trace
- LinkedIn Sales Navigator, Clay enrichment, and similar tools don't leave public signals
- Try the Apify profiler if you only ran free-only mode
"SPF has Google only but they use Smartlead/Instantly"
- This is normal. Smartlead and Instantly typically connect to Google Workspace mailboxes via SMTP and send through Google — so SPF passes via Google's include. The cold email tool itself doesn't need its own SPF entry.
- Look for Smartlead's
open.sleadtrack.comin TXT records or website source as confirmation.
"Apify profiler timed out"
- Some sites take longer to load. The profiler has a 3-minute timeout.
- Retry once. If it fails again, rely on DNS + source code analysis.
"artisan.ai resolves but redirects to Afternic"
- The domain is parked/for sale. Check common alternatives:
.co,.com,.io. - Wildcard DNS (all subdomains resolve to the same IP) is a sign of a parked domain.
Links
- Apify Technology Profiling Engine
- Apify API Token
- MXToolbox — manual verification
- Spamhaus Domain Lookup
© majiayu000, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/analysis/tech-stack-teardown of majiayu000/claude-skill-registry.
- SKILL.md
- metadata.json
Open the folder on GitHubat commit 2d14a69
Used in 2 other repositories
We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in majiayu000/claude-skill-registry, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Tech Stack Teardown 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 |
|---|---|---|---|---|---|---|
| Tech Stack Teardown this skillmajiayu000/claude-skill-registry | 666 | 2 repos | ~3.1k | Automated safety check: Notes | MIT | |
| Ops LeadgenLifecycle-Innovations-Limited/claude-ops | 540 | — | ~990 | Automated safety check: Notes | MIT | |
| Apify Buying Signal Detectionapify/awesome-skills | 264 | — | ~5.1k | Automated safety check: Notes | Apache-2.0 | |
| Auto Research Publicgrowthenginenowoslawski/coldoutboundskills | 742 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Pain Language Engagersgooseworks-ai/goose-skills | 1.2k | 1 repos | ~2.1k | Automated safety check: Notes | MIT | |
| Etsy Shop Sales Historysickn33/agentic-awesome-skills | 47k | 1 repos | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Apify Buying Signal Detection
apify/awesome-skills
Set up a recurring buying-signal detection pipeline that finds companies showing buying intent across three signal types — job postings (hiring for the persona), fundraising events (recent raises)…
Auto Research Public
growthenginenowoslawski/coldoutboundskills
Autonomous cold email campaign launcher. An agent skill from growthenginenowoslawski/coldoutboundskills.
Pain Language Engagers
gooseworks-ai/goose-skills
Find warm leads by searching LinkedIn for pain-language posts — the frustrations, complaints, and operational struggles your ICP talks about publicly.
Etsy Shop Sales History
sickn33/agentic-awesome-skills
Read Etsy shop sales counters, deltas, and breakout flags from Apify Actor publicrecords/etsy-shop-velocity (MCP panel snapshot).
Personalize Message
Othmane-Khadri/YALC-the-GTM-operating-system
Generate a personalized outbound message (LinkedIn DM or cold email) for a single prospect by combining a template with the lead's profile, company, and recent signals.
More from majiayu000/claude-skill-registry
All 1,273 skills in this repoDeep Research
majiayu000/claude-skill-registry
Multi-source deep research using firecrawl and exa MCPs. An agent skill from majiayu000/claude-skill-registry.
Exa Search
majiayu000/claude-skill-registry
Neural search via Exa MCP for web, code, and company research.
Fal AI Media
majiayu000/claude-skill-registry
Unified media generation via fal.ai MCP — image, video, and audio.
Pyzotero
majiayu000/claude-skill-registry
Interact with Zotero reference management libraries using the pyzotero Python client.
Bgpt Paper Search
majiayu000/claude-skill-registry
Search scientific papers and retrieve structured experimental data extracted from full-text studies via the BGPT MCP server.
Bio Alignment Pairwise
majiayu000/claude-skill-registry
Perform pairwise sequence alignment using Biopython Bio.Align.PairwiseAligner.
Related
Categories
Questions about Tech Stack Teardown
What does Tech Stack Teardown do?
Reverse-engineer a company's sales and marketing tech stack from public signals. Tech Stack Teardown is an agent skill from majiayu000/claude-skill-registry. Reverse-engineer a company's sales and marketing tech stack from public signals.
When should I use Tech Stack Teardown?
Tech Stack Teardown fits situations like: tasks that involve Web scraping; tasks that involve Transactional email; tasks that involve Cold outreach.
How do I install Tech Stack Teardown in Claude Code?
Run `npx skills add majiayu000/claude-skill-registry --skill tech-stack-teardown -a claude-code`. Or copy the skill folder (skills/analysis/tech-stack-teardown in majiayu000/claude-skill-registry) into .claude/skills/tech-stack-teardown in your project. Claude Code loads it when a task matches its description.
How do I install Tech Stack Teardown in Codex?
Run `npx skills add majiayu000/claude-skill-registry --skill tech-stack-teardown -a codex`. Or copy the skill folder (skills/analysis/tech-stack-teardown in majiayu000/claude-skill-registry) into .agents/skills/tech-stack-teardown in your project. Codex loads it when a task matches its description.
Can I use Tech Stack Teardown 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 majiayu000/claude-skill-registry --skill tech-stack-teardown -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tech-stack-teardown, .gemini/skills/tech-stack-teardown, .github/skills/tech-stack-teardown and .opencode/skills/tech-stack-teardown in your project.
What does Tech Stack Teardown need to run?
Going by SKILL.md and its folder, Tech Stack Teardown needs the command-line tools its instructions call (python3, pip3 and curl) and credentials named APIFY_API_TOKEN. Our summary lists: Python 3; A credential in APIFY_API_TOKEN.
Does Tech Stack Teardown access the network?
SKILL.md names 4 domains. In commands or code: console.apify.com; the agent is likely to contact it when it follows the instructions. As links in the text: apify.com, mxtoolbox.com and check.spamhaus.org. This is read from the text; nothing was executed.
Is Tech Stack Teardown safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Tech Stack Teardown use?
Tech Stack Teardown is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Tech Stack Teardown use?
About 3.1k tokens (SKILL.md is roughly 12k 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 Tech Stack Teardown?
Skills that share tags, products or a category with Tech Stack Teardown: Ops Leadgen (Lifecycle-Innovations-Limited/claude-ops, 540 stars), Apify Buying Signal Detection (apify/awesome-skills, 264 stars), Auto Research Public (growthenginenowoslawski/coldoutboundskills, 742 stars) and Pain Language Engagers (gooseworks-ai/goose-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Tech Stack Teardown?
majiayu000 (a GitHub user) maintains it in majiayu000/claude-skill-registry, which has 666 GitHub stars. The repository holds 1,273 skills in this directory. The repository was last updated on October 7, 2026.
Source: majiayu000/claude-skill-registry on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.