Skip to main content
Home · 首页/Testing · 测试与质量/business contact social links skill
#66
Ranked #66 of 68 in this category· 该品类排名 #66 / 共 68 个

business contact social links skill

by browser-act·18d ago

This skill helps users automatically extract official website and social media profiles. Agent should proactively apply…

Claude CodeCodexLow risk · 低风险open source · 开源
Editor's verdict· 编辑结论

Auto-published by GitHub discovery based on star threshold.

— Editorial team · 编辑团队

Install via Skills CLI

Use npx skills add to install this skill into the selected agent. Phase 0 commands are generated from source rules, not verified.

Codex
npx skills add https://github.com/browser-act/skills/blob/main/solutions/lead-generation/business-contact-social-links-skill/SKILL.md -g -a codex -y

Drop `-g` to install project-locally

Best for适合什么场景

  • High-star GitHub skill discovery candidate.

Not for不适合什么场景

  • Sensitive or production workflows without local review.

vs alternativesvs 其他选择

Full compare table完整对比表 →
#1QA Loop

Open the product, try the flow, fix what breaks, repeat.

4.9·15k stars
diff · 差异Best browser QA pick when you need evidence to leave a paper trail. Each run produces screenshots, console diffs, and a reproducible action log — much harder for stakeholders to wave off than "I tested it locally." Works well as a pre-merge gate and for filing bugs with repro steps attached. Not for unit tests, and not for authenticated production sessions where the screenshot itself becomes a data risk.
#2GStack QA

Open the app, test the flow, fix what breaks.

4.8·80k stars
diff · 差异Best when browser QA needs to close the loop — find the bug, propose the fix, verify the fix, leave evidence. Where qa-loop emphasizes evidence trails for stakeholder reporting, gstack-qa emphasizes shipping the fix in the same session. Strongest on frontend refactors and visual regressions. Same screenshot data-risk caveat as qa-loop: don't point it at authenticated production sessions where the screenshot itself becomes a leak.
#3Canary Watch

Verify the live deploy before users tell you it is broken.

4.6·8.2k stars
diff · 差异Best for the 10–30 minutes right after a deploy hits production, when "we already verified in staging" starts to wear thin. Hits a curated list of critical routes, watches for console errors, broken pages, and visual diffs against baseline. Lightweight by design — it is not a synthetic monitoring platform. Pair with release-briefing for the comms side. Don't use it as a substitute for pre-merge QA; that's qa-loop or gstack-qa's job.

Side-by-side compare维度对比

Key differences with same-lane alternatives
this skill · 当前business contact social links skillQA LoopGStack QACanary Watch
Rating · 评分4.94.84.6
Stars · 星标1.2k15k80k8.2k
Risk · 风险Low risk · 低风险Medium risk · 中风险Medium risk · 中风险Medium risk · 中风险
Best for · 最适合High-star GitHub skill discovery candidate.Browser smoke testsOpen the app, test the flow, fix what breaks.Verify the live deploy before users tell you it is broken.
Not for · 不适合Sensitive or production workflows without local review.Pure unit testingWorkflows that require stronger human review than this catalog entry documents.Workflows that require stronger human review than this catalog entry documents.

Audit notes审计备注

last reviewed 2026-06-03 · 复查
Source源码open on GitHub · 公开
Author作者community · 社区!
Network网络访问read-only · 只读
Filesystem文件写入sandboxed · 沙箱
Dependencies依赖audited · 已审计
Telemetry遥测none · 无
Skill Market
Find the best AI skills for the job·按品类找最好用的 AI 技能
v0.4 · 1252 skills indexed · last review 2026-06-03