agentleFS
Sign inStart free
jstanxjstanx/aeo-toolkit/skills/community-and-reviews/SKILL.md

community-and-reviews

Skill2 starsChanged 5 months agoMITView on GitHub

Build the community and review-platform presence answer engines lean on — authentic participation in Reddit, forums, and Q&A communities, plus a strong, current presence on review sites like G2, Capterra, and Trustpilot. Works for any business, B2B or B2C, product or service. Use when the request is to improve AI visibility via Reddit or communities, get cited from forums, build review-platform presence for AI, or understand why competitors appear in AI answers from community and review sources. Pairs with digital-pr and comparison-content.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read aeo-foundation.md for the category, audience, competitors, and where the audience actually congregates.

    line 34
  2. Distinctive:

    Disclose affiliation: When relevant, be transparent about working for the brand — honesty is the signal, and most communities require it.

    line 44

≈ “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

Community and Reviews

This skill builds presence in the communities and review platforms answer engines trust as proxies for real experience. Engines that retrieve in real time lean heavily on discussion sites (Reddit, forums, Q&A) and review platforms — they read these as authentic, peer-validated signals. For many commercial prompts, a strong review-platform presence is close to a precondition for being recommended at all. This skill earns that presence honestly. It works for any business, B2B or B2C.

When to use this skill

  • A category where engines cite Reddit, forums, or review sites heavily (test to confirm).
  • Building or improving review-platform presence (G2, Capterra, Trustpilot, vertical sites).
  • Establishing authentic community participation that earns mentions.
  • Understanding why competitors surface from community/review sources.

Before you start

Read aeo-foundation.md for the category, audience, competitors, and where the audience actually congregates. If it is missing, point to the aeo-foundation skill. Confirm which communities and review sites engines cite for your prompts (use competitor-ai-analysis).

Community presence (Reddit, forums, Q&A)

  • Participate authentically. Be genuinely helpful in the relevant communities; answer questions, share real expertise. Communities (and engines reading them) reward authenticity and punish thinly veiled promotion.
  • Disclose affiliation. When relevant, be transparent about working for the brand — honesty is the signal, and most communities require it.
  • Earn mentions, don't plant them. Unlinked, organic mentions of the brand by real community members carry weight; manufactured or astroturfed threads are a reputational and policy risk and can backfire badly.
  • Be where the category lives. Identify the specific subreddits/forums tied to your prompts and show up consistently, not once.

Review platforms (G2, Capterra, Trustpilot, vertical sites)

  • Establish presence first. Engines often require a review presence to include a brand in commercial answers — a complete, claimed profile is table stakes.
  • Earn reviews ethically. Prompt satisfied customers to review through legitimate, compliant flows; never buy or fabricate reviews (detectable, against policy, and trust-destroying).
  • Keep profiles current and accurate. Up-to-date descriptions, categories, and responses; consistent with the brand's entity facts (see entity-optimization).
  • Engage with feedback. Responding to reviews — especially critical ones — adds fresh, credible signal and shows trustworthiness.
  • Pick the right platforms. B2B software leans G2/Capterra; consumer leans Trustpilot and category-specific sites; choose where your buyers and the engines actually look.

Workflow

  1. Confirm the sources engines cite for your prompts (community vs. review, which sites).
  2. Prioritize the few communities and platforms that matter for your category.
  3. Build review presence: claim/complete profiles; launch an ethical review-generation flow; respond to existing reviews.
  4. Establish community presence: a sustained, authentic participation plan with disclosure.
  5. Keep facts consistent with the entity across every profile.
  6. Measure mentions and citations sourced from these surfaces (see ai-visibility-tracking).

Output format

  • A priority map of communities and review platforms for the category, with the current gap.
  • A review plan: profiles to claim/complete and an ethical review-generation approach.
  • A community plan: where to participate, how, with disclosure guidelines.
  • (assumption) tags where source influence was inferred.

Common pitfalls

  • Astroturfing or fake reviews — high risk, detectable, and trust-destroying.
  • Promotional drive-bys in communities that earn downvotes and bans.
  • Claiming a review profile and letting it go stale.
  • Investing in platforms your buyers and engines do not actually use.

Related Skills

  • digital-pr — the broader earned-corroboration program this fits inside.
  • comparison-content — community and review-sourced "best of"/alternatives.
  • entity-optimization — consistent facts across every community/review profile.
  • competitor-ai-analysis — shows which community/review sources engines cite.

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