agentleFS
Sign inStart free
ZoolCoderZoolCoder/findable/skills/schema/SKILL.md

schema

Skill0 starsChanged 30 days agoMITView on GitHub

Add and fix schema.org structured data (JSON-LD) so pages qualify for Google rich results and read clearly to AI search. Covers Organization, LocalBusiness, JobPosting, BreadcrumbList, Article, Product, Event and FAQ, and Google's policies on each. Use when the user asks about "schema", "structured data", "JSON-LD", "rich results", "rich snippets", or a findable schema.* finding.

34 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use popups, paywalls and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 8 projects that use this

  • CesarjoquinSkill

    paywalls

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

    Also in 8 projects that use this

  • tdiminoSkill

    sms

    Send, read, listen, respond, and manage SMS conversations via Telnyx and Twilio. Supports 8 phone numbers across both providers with auto-detection, conversation threading, MMS, real-time inbound listening, background watcher, batch reply processor, and soul-aware auto-reply. 10 Python scripts for SMS operations.

    Also in 8 projects that use this

  • timruebenachSkill

    directory-submissions

    When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Also use when the user mentions "directory submissions," "submit to directories," "backlinks from directories," "list my product," "submit to Product Hunt," "BetaList," "TAAFT," "Futurepedia," "G2 listing," "Capterra listing," "AlternativeTo," "SaaSHub," "AI directories," "MCP registry," "agent directory," "dofollow backlinks," "launch directories," or "directory tracker." Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign. For the broader launch moment, see launch-strategy. For programmatic SEO pages that should live behind these backlinks, see programmatic-seo. For AI citation optimization, see ai-seo.

    Also in 8 projects that use this

  • roerohanSkill

    prospecting

    When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.

    Also in 8 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.

    Also in 5 projects that use this

  • +6 more from Cesarjoquin

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 1 is distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 30 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Write the matching rules into schema: in findable.yaml so every future page is checked.

    line 21
  2. Very specific:

    When a job closes, expire it one of the three ways Google accepts: a validThrough in the past, removing the page (404/410), or removing the …

    line 27
  3. Very specific:

    Never: keep a filled job marked up as open (a future or missing validThrough on a closed role).

    line 28
  4. Very specific:

    Ask whether a flagged job is really closed before fixing it: an open role needs a real validThrough, not less markup.

    line 29
  5. Distinctive:

    Use the Indexing API only for JobPosting and livestream pages.

    line 31
  6. Very specific:

    No self-serving reviews: an AggregateRating a business gives itself is not eligible for stars.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 30 edited versions of this file we could read. “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

Structured data

Choose the types

PageTypeNotes
HomeOrganization (or the most specific subtype)name, url, logo, sameAs (official profiles), contactPoint
Each office or shopLocalBusiness subtype, one per locationname, address, telephone, url, openingHours, geo
A job's own pageJobPostingone per page; never on a list of jobs
Every page below homeBreadcrumbListpositions 1, 2, 3; every item but the last has a URL
Blog and newsArticle / NewsArticleheadline, datePublished, dateModified, author, image
Products, eventsProduct, Eventprice and availability, or date and place

Write the matching rules into schema: in findable.yaml so every future page is checked.

JobPosting (Google job search)

  • Required: title, description (HTML allowed), datePosted, hiringOrganization with a name, jobLocation (or applicantLocationRequirements with jobLocationType: TELECOMMUTE).
  • Recommended: baseSalary, employmentType, validThrough. Job search filters on them.
  • When a job closes, expire it one of the three ways Google accepts: a validThrough in the past, removing the page (404/410), or removing the JobPosting markup. Say on the page that the role is filled and link to open ones.
  • Never keep a filled job marked up as open (a future or missing validThrough on a closed role). Expired listings left open are a policy violation and can cost the whole site its job listings.
  • Ask whether a flagged job is really closed before fixing it: an open role needs a real validThrough, not less markup.
  • Whenever you set a future validThrough, tell the owner in the same reply how to expire the posting the day the role is filled (one of the three ways above). A date alone is not a fix.
  • Use the Indexing API only for JobPosting and livestream pages. Google limits it to those.

Rules Google enforces

  • Mark up only what the page shows. Every value in the JSON-LD must be visible to the reader.
  • No self-serving reviews: an AggregateRating a business gives itself is not eligible for stars. Never write ratings or reviews that real customers did not give.
  • FAQ rich results show only for well-known government and health sites. FAQPage markup still helps AI answers, but promise no stars or dropdowns.
  • HowTo rich results are gone. Skip HowTo markup.
  • One entity, one name: the Organization name matches the logo, the site and the Google Business Profile. findable's local.nap.mismatch checks this when business: is set.

Check

Rebuild, then findable audit, then Google's Rich Results Test on one page of each type. Fix in the JSON-LD builder, not page by page.

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