noique
- 12 skills
- 0 followers
- 17 hours ago last updated
- ▌ Fetchlib · noique bundleA compliance-first page-fetch waterfall for the repo's scraping skills: tiered backends that escalate only when the current tier is genuinely blocked — L1 curl_cffi (TLS/JA3 impersonation, no JS) → L2 r.jina.ai (JS render to clean markdown) → L3 pluggable nodriver/browser → L4 opt-in paid unblocker — wrapped in api-pacer + AIMD per-domain rate control, a per-domain circuit breaker, JSONL fetch telemetry (url/tier/status/blocked/bytes/ms), robots.txt honoring, and optional Thompson-sampling backend learning (learn=True) because the best tier varies by site AND by IP. Use when the user wants to fetch or scrape pages without getting 403'd, needs one shared fetch layer instead of ad-hoc curl in every script, or asks which fetch method to use for a specific hard site and whether it's time to pay for an unblocker. Triggers on "fetchlib", "抓取被封了", "403 抓不到", "换个方式抓这个站", "统一抓取层", "要不要上付费代理/unblocker", "curl_cffi 还是 Jina", "抓竞品页面老失败", "scrape without getting blocked", "fetch waterfall", "which fetcher for this site".
- ▌ API Pacer · noique bundlePolite request pacing for any scraping or API-hitting skill: a zero-dependency Python pacer (Pacer, polite_get) that paces off the server's own rate-limit response headers (x-ratelimit-remaining / reset, with reddit / github / generic presets) and does AWS-style full-jitter exponential backoff on 429 / 503 / Retry-After. Use when the user wants to stop getting rate-limited or soft-blocked while looping over an API or a site, add sane delays + retries to a fetch loop, tune rps / safety / max_backoff, or asks whether random "human-like" Gaussian sleeps help (they don't — read the real budget instead). Triggers on "api-pacer", "限速", "请求配速", "加个礼貌延迟", "抓取被 429 了", "怎么才不被限流", "退避重试", "打 API 太快被封", "rate limit backoff", "429 retry-after", "polite scraping delay", "throttle my requests". Pairs with /fetchlib (uses it as the control layer) and is an opt-in drop-in for /reddit-voc, /serp-content-teardown, /outbound-prospecting and /trustpilot. NOT an anti-bot tool — it does not rotate IPs, spoof fingerprints, or solve
- ▌ Browser Fetch · noique bundleA shared, pluggable real-browser rendering backend (default engine Selenium, headless, optional proxy) that mounts as fetchlib's L3 tier, so multiple skills stop each writing their own Selenium — returns (status, html, headers), normalizes anti-bot challenge pages to status=403 so the waterfall correctly marks them blocked, and exposes register_engine() for opt-in nodriver / camoufox / scrapling. Use when the user needs JS-rendered HTML for a scrape, hits a page that comes back empty or thin without a browser, wants one reusable browser layer across scraping skills, or wants to route a fetch through a proxy. Triggers on "browser-fetch", "要真浏览器渲染", "这站要跑 JS 才有内容", "用 Selenium 抓一下", "挂个浏览器后端", "curl 抓不到内容", "带代理抓", "render JS to scrape", "headless browser fetch", "this site needs a browser". Pairs with /fetchlib (register it as the browser L3 tier, only after curl_cffi / Jina fail) and /api-pacer; deliberately does NOT replace the existing Selenium inside /trustpilot. Honest limit (2026-06, datacenter IP): it t
- ▌ Reddit Voc · noique bundleMine Reddit for pre-purchase Voice-of-Customer (VOC) insights for a DTC brand or Amazon product. Use when the user wants to understand what overseas users actually say about a category before buying — pain points, value-system landmines, jargon, alternatives. Triggers on "Reddit VOC", "Reddit 用户洞察", "海外用户怎么说我们品类", "购买前 VOC", "find subreddits for [category]", "what do Redditors think of [product]", "听用户声音", "Reddit 调研", "海外用户痛点". Pairs with /trustpilot-voc-deep (post-purchase) and /amazon-market-research (post-purchase).
- ▌ Contact Extractor · noique bundleMulti-source contact email extraction for KOL / media prospect rows. Given a CSV with personal_site / youtube / podcast_apple columns (e.g. output of linktree-expander or media-press-discovery), enrich each row with up to 3 ranked candidate emails + source label + confidence tier (high/medium/low/none). Triggers on "find contact email", "extract email from creator profile", "deep dig contact info", "enrich KOL contacts".
- ▌ Linktree Expander · noique bundleExpand a list of Linktree handles (e.g. example_creator, brand_x) into a full table of each user's social handles + outbound links + bio + visible email. Use when you have a list of Linktree slugs from KOL discovery (output of backlink-kol-extractor or similar) and need to enrich them into actionable per-creator profiles. Triggers on "expand linktree", "linktree to social handles", "enrich linktree creators", "find IG/TikTok behind linktree".
- ▌ Backlink Kol Extractor · noique bundleExtract KOL, influencer, media, and partnership prospects from Semrush competitor backlink/refdomains/competitors xlsx data. Use when the user wants to find influencers, KOLs, review sites, media contacts, PR targets, affiliate partners, or forum communities from Semrush data exports. Triggers on "find KOL", "extract influencers from backlinks", "find review sites", "find media contacts", "partnership prospects", "who links to competitors", "backlink analysis for outreach", "find blogs that review", "discover influencer partners", "find collaboration opportunities from SEO data".
- ▌ Security Precommit Check · noique bundlePre-commit security scanner for git repos — blocks API keys, proxy credentials, private keys, and project-specific secrets before they reach a remote. Provides a central rule definition + per-repo customization + one-line installer that wires up `.git/hooks/pre-commit`. Use when you want to prevent accidental credential / identity / brand leaks across multiple repos. Triggers on "set up pre-commit security check", "block API keys in commits", "git secret scanner", "prevent credential leaks", "protect identity isolation in public repos".
- ▌
- ▌ Linkedin Prospecting · noique bundleFind overseas B2B decision-makers via Google/Bing reverse-search of LinkedIn profiles, enrich with email/phone via legitimate SaaS tools, then run a 4-touch outreach sequence (connection request → accepted-DM → follow-up → channel-switch) with reply-rate-tested templates. Use when a foreign-trade / cross-border / DTC seller wants to build a targeted list of buyers, procurement managers, distributors, or CEOs on LinkedIn — without paying LinkedIn Sales Navigator and without burning Connection requests on dead profiles. Sister skill to `google-whatsapp-prospecting`. Trigger phrases include "find LinkedIn buyers", "LinkedIn 反查", "Google 反查 LinkedIn CEO", "外贸 LinkedIn 开发", "LinkedIn 私信模板", "领英开发客户", "LinkedIn DM templates", "find decision makers LinkedIn".
- ▌
- ▌ Google Whatsapp Prospecting · noique bundleFind B2B buyers' WhatsApp contacts at scale by Google-dorking product + region + WhatsApp signals, then validate, enrich, and run a compliant cold outreach sequence. Use when a foreign-trade / cross-border / DTC seller wants to build a targeted outbound list of importers, distributors, wholesalers, or end-buyers reachable on WhatsApp — without relying on paid B2B databases (Alibaba, IndiaMART, Kompass). Trigger phrases include "find WhatsApp leads", "Google reverse-lookup WhatsApp", "外贸 WhatsApp 开发客户", "Google 反查 WhatsApp", "外贸找客户公式", "海外采购商 WhatsApp", "拓客 WhatsApp 群发".