agentleFS
Sign inStart free
hebertzhuhebertzhu/agent-foundry/skills/saas-site-research/SKILL.md

saas-site-research

Skill0 starsChanged 8 months agoMITView on GitHub

用于做 SaaS 官网 / 营销站 / 首页的研究、策略和报告：当用户说“联网看看别人家怎么做官网”“研究 3-5 个同类产品首页”“别人首屏一句话、CTA、SEO 文案怎么写”“先别改页面，先给我一份报告”“判断首页该做品牌入口还是转化页”这类需求时使用。聚焦竞品官网研究、首页结构、价值表达、CTA、品牌入口、proof、SEO / 营销表达与动效策略，并结合当前项目输出可落地建议。Prefer `frontend-design` when the user wants to 直接改页面、产出具体前端实现或视觉稿；Prefer `brainstorming` when 业务目标、受众或约束还没定清；Combine with `planning-with-files` when 研究范围大、需要分阶段沉淀或持续跟踪。

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep examples generic, privacy-safe, and portable across hosts.

    line 21
  2. Distinctive:

    Do not jump straight into visual edits when the user asked for research first.

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

saas-site-research

Intent

  • 用于做 SaaS 官网 / 营销站 / 首页的研究、策略和报告：当用户说“联网看看别人家怎么做官网”“研究 3-5 个同类产品首页”“别人首屏一句话、CTA、SEO 文案怎么写”“先别改页面，先给我一份报告”“判断首页该做品牌入口还是转化页”这类需求时使用。聚焦竞品官网研究、首页结构、价值表达、CTA、品牌入口、proof、SEO / 营销表达与动效策略，并结合当前项目输出可落地建议。Prefer frontend-design when the user wants to 直接改页面、产出具体前端实现或视觉稿；Prefer brainstorming when 业务目标、受众或约束还没定清；Combine with planning-with-files when 研究范围大、需要分阶段沉淀或持续跟踪。

Default operating pattern

  1. Clarify audience, surface, success metric, and implementation boundary.
  2. Study relevant patterns, references, or constraints before proposing a direction.
  3. Define structure, interaction, copy, and visual hierarchy with a reusable rationale.
  4. Pressure-test accessibility, motion, maintainability, and platform fit.
  5. Return a concise recommendation and the next implementation move.

Pack fit

  • Included in: product-design
  • Keep examples generic, privacy-safe, and portable across hosts.

Boundary

  • Do not jump straight into visual edits when the user asked for research first.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free