← FindAffiliatesCONTENT HISTORY
WHAT CHANGED
Update to FindAffiliates
Snapshot Oct 24, 2026 · 13:35 UTC · version 0.1.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save FindAffiliates and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Answer affiliate strategy and FindAffiliates product questions using relevant website guides, FAQs, tool documentation, and editorial or privacy pages with source links.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 283
}
],
"name": "research-affiliate-guides",
"skill_md_contents": "---\nname: research-affiliate-guides\ndescription: Answer affiliate strategy and FindAffiliates product questions using relevant website guides, FAQs, tool documentation, and editorial or privacy pages with source links.\n---\n\n# Read relevant guides and product information\n\nUse the available browser or public web retrieval. Start with the resource that matches the question:\n\n- Guides: https://www.findaffiliates.online/blog\n- FAQs: https://www.findaffiliates.online/find-affiliates-faq\n- Tool documentation: https://www.findaffiliates.online/tools\n- Recent program additions: https://www.findaffiliates.online/latest-affiliate-programs\n- Editorial provenance: https://www.findaffiliates.online/editorial-policy\n- Privacy: https://www.findaffiliates.online/privacy-policy\n- Terms: https://www.findaffiliates.online/terms-of-service\n\nFollow actual relevant article or tool links. Canonical blog paths use `/blog/{slug}`; `/blogs` is an alias. Supported `.md` twins can simplify retrieval if the host can read them. `/llms.txt` is useful for discovering guides but has only a partial program list; `/llms-full.txt` contains blog and product material and can have older product claims. Fetch targeted pages rather than the full corpus for each answer.\n\nCheck an article's date and source context. Preserve uncertainty about changing program terms, eligibility, rates, or access. A current program profile or provider-source record can differ from an older guide; say which source supports each claim. Do not present marketing superlatives or visibility promises as independent verification.\n\nAnswer the question with relevant source links, then offer the specific existing tool or page that helps carry out the advice. Distinguish directory programs from people to recruit: the site does not currently provide a verified public creator database, content calendar, or bookmark folders. Current calculator and finder access depends on the user's session.\n\nExplain existing entitlements only when relevant to a blocked feature. Do not advertise digital subscriptions, listing packages, or checkout links, and do not accept terms or sign up for programs. Reading a website page does not authorize account actions. If web access is blocked/unavailable, give the resource link and state which details were not verified. Never use em dashes.\n"
}SHA-256 of public snapshot: 607070e44105625a85eee5dc9f5a999a763594dea066c2f1feaf62beb761d4d6