This page is for people who work in ChatGPT, Claude, or similar assistants that can search a curated library (for example product rules, playbooks, or internal guides) instead of relying only on what the model remembers from training.
You do not need to know how the library is stored. If your workspace or project already connects the assistant to that library, treat this as how to ask so answers stay grounded, specific, and useful. On Kuudo, Amazon Agent Atlas is one way that library is connected; the habits below apply to any similar setup.
What Changes When a Library Is Connected
A connected library is searchable text your agent can pull in during the conversation. It is not magic: the assistant finds passages that match your question, then reads them to answer. Clear questions and explicit goals produce better retrieval than vague ones.
You should expect
- Answers that quote or follow your organization’s material when it is relevant.
- Less invention on topics where your library is the source of truth.
- The assistant to say when it cannot find a match, instead of guessing.
How to Ask
Use the same habits you would use with a sharp colleague who has access to your file share.
- Name the domain in plain language (Amazon listings, sponsored ads, compliance, style guides).
- Say the output shape you want: checklist, table, rewrite, pros and cons, email draft, bullet talking points.
- Add constraints: audience (seller, executive, new hire), region, tone, or “only use our library; say if something is missing.”
- One main task per message when possible. Long laundry lists get partial answers.
Use Case: Category or Channel Rules
Use this when you need how we title, bullet, or structure listings for a specific category or channel.
You might write
Pull our style guidance for Amazon Grocery listings. Summarize title patterns and bullet order in a short checklist I can hand to a copywriter.
You might write
We are launching a pet food SKU. What does our library say about species, life stage, and parent/child titles? Give me a do/don’t list.
What you should get
- A compact checklist or bullets tied to your guides, not generic e-commerce advice.
- Explicit callouts when your library distinguishes sub-categories (for example food vs toys).
Use Case: Rewrite or Strengthen Copy
Use this when you have draft listing text and want it aligned to your stored rules.
You might write
Here is our draft title and five bullets for a chromebook. Rewrite them to match our Computers style guide. Keep the same facts; flag anything we should verify on Seller Central.
You might write
Rewrite these bullets for a baby car seat listing in a calmer, compliance-first tone. Cite which rules from our library you applied.
What you should get
- Revised copy plus a short “why” tied to your library (title formula, claim limits, required attributes).
- Flags where the library says to verify with compliance or live templates.
Use Case: Compare Two Approaches
Use this when you are choosing between strategies and want the assistant to ground the tradeoffs in your material.
You might write
Compare “keyword-stuffed titles” vs “spec-first titles” for consumer electronics accessories using only our guidance. End with a recommendation for a three-SKU cable line.
What you should get
- A side-by-side or short table grounded in your docs, plus a clear recommendation and assumptions stated explicitly.
Use Case: Onboarding and Training
Use this when someone new needs the shape of a domain without reading hundreds of pages.
You might write
New hire starts Monday on Amazon Ads reporting. Give a 10-minute spoken overview outline: what to read first, three concepts that confuse people, and five questions they should ask the account lead.
You might write
What topics does our library cover under vendor operational compliance? List them as a syllabus with one sentence each on why it matters.
What you should get
- A syllabus, outline, or FAQ-style map that reflects what is actually in the library.
Use Case: Pre-Flight Before a Launch or Audit
Use this when you want a last pass against stored rules before publishing or before a client call.
You might write
We are about to publish a supplements detail page. Scan against our Health & Personal Care guidance: structure/function vs disease claims, disclaimer placement, and title formula. Output pass / fix / escalate.
You might write
Tomorrow’s meeting: sponsored ads bidding. List the top five risks or misconceptions our library warns about, with one example question to ask the client for each.
What you should get
- A prioritized review list with “fix” vs “escalate to legal/compliance” style buckets when your material supports that split.
Use Case: “What Do We Actually Say About X?”
Use this for pointed fact finding when rumors or forum advice conflict with your standards.
You might write
What does our library say about refurbished computer listings and disclosure wording? Quote short phrases if helpful.
You might write
Find anything we have on live plants or hardiness zones in listing copy. If we have nothing, say so clearly.
What you should get
- Direct excerpts or faithful paraphrases with scope (“this is from the Garden guide, not legal advice”).
- A clear “not found in library” when there is no match.
Limits and Expectations
- Staleness: Your library reflects the documents that were indexed. Amazon templates, policies, and UI change; always confirm critical details in Seller Central or official sources when stakes are high.
- Not legal advice: Guides summarize patterns and internal standards. Compliance decisions stay with your counsel and account owners.
- Retrieval is not perfect: Unusual wording or missing tags in source files can make matches weaker. Rephrase or add a keyword from your domain if the first answer feels thin.
- Privacy: Do not paste secrets into chats unless your organization approves that workflow. Ask about sanitized examples when demonstrating issues.
Related Material
- Amazon Agent Atlas — Kuudo’s curated Amazon operating library and how it fits agents.
- Claude quick start and ChatGPT quick start — connect a client, then use the prompts above.
For the open-source Chroma MCP knowledge pipeline (developers), see the chroma-mcp repository README and agent instructions at the repository root.