Update to Bull AI

{
  "name": "moat-and-peers",
  "description": "Map management-claimed advantages against listed peers.",
  "included_files": [],
  "skill_md_contents": "---\nname: moat-and-peers\ndescription: Map management-claimed advantages against listed peers.\n---\n\n# Management-Claimed Advantages and Peers\n\nUse this skill when a user asks what competitive advantages management claims for an Indian listed company and how those claims relate to a bounded set of listed peers.\n\n## Internal workflow\n\n1. Resolve the subject company with `search_companies`.\n2. Retrieve its sectors, industries, and company category with `get_company_classification`.\n3. Retrieve a bounded peer set with `get_company_peers`; follow pagination only when the requested scope requires it.\n4. Treat each peer row's `industries` as the subject company's industry bucket under which that peer was matched. Never present it as the peer's own classification.\n5. Search subject-company filings, annual reports, transcripts, and presentations with `search_company_documents` for management statements about competitive advantages, distribution, brands, capabilities, customer relationships, cost position, technology, scale, or other relevant factors.\n6. Inspect each cited passage with `get_document_chunks`. Record the exact claim, speaker or attribution when available, period, and document citation.\n7. Label these as management-claimed advantages, not verified moats.\n8. By default, use the peer set only as market context. Do not infer peer ranking, market share, similarity score, moat strength, durability, or financial superiority.\n9. If the user requests an evidence-based peer comparison, select a small, disclosed peer subset and retrieve comparable company-document evidence for each peer. Compare only the same supported dimension and period.\n10. If comparable peer evidence is unavailable, state that the requested stack-up cannot be established from the available evidence.\n\n## Public answer\n\nUse these sections:\n\n1. **Company classification** — sector, industry, and category with returned source metadata.\n2. **Management-claimed advantages** — claim, context, evidence, and document citation.\n3. **Peer context** — bounded peer list without unsupported ranking.\n4. **Evidence-based comparison** — only dimensions supported by comparable cited passages.\n5. **Interpretation and limitations** — clearly separated model analysis, missing peer evidence, and pagination limits.\n6. **Sources**.\n\nSuggested claim table:\n\n| Management-claimed advantage | Supporting passage | Relevant peer context | What the evidence supports | Source |\n|---|---|---|---|---|\n\n## Monetary units and currency conversion\n\n- Prefer Indian rupees crores (`₹ crore`) for monetary values in tables, comparisons, calculations, and summaries.\n- Convert reported INR scales exactly: ₹1 lakh = ₹0.01 crore; ₹100 lakh = ₹1 crore; ₹1 million = ₹0.1 crore; ₹10 million = ₹1 crore; ₹1 billion = ₹100 crore.\n- Preserve the source's reported amount when it is in another currency, followed by the estimate in brackets: `US$X million (≈₹Y crore)`.\n- Use the best defensible period-appropriate FX rate: transaction-date rate for dated events, period-end rate for point-in-time balances, and period-average rate for revenue, costs, cash flow, or other period flows.\n- Prefer an exchange rate stated in the company document. Otherwise use a reputable retrieved FX source. State the rate, date or period, source, and formula: `foreign-currency amount × INR per foreign-currency unit ÷ 10,000,000 = ₹ crore`.\n- Prefix converted figures with `≈` and use sensible precision; do not imply more accuracy than the FX input supports.\n- Never invent an exchange rate. If no defensible rate is available, retain the original currency and state that an INR-crore estimate could not be produced.\n\n## Sources, citations, and boundaries\n\n- Do not mention tool names, call order, arguments, cursors, backend identifiers, schemas, or retrieval narration in the public answer.\n- For document-backed claims, cite only returned company-document URLs and pages. Never invent missing citation elements.\n- For classification, render returned source labels and `as_of` values as source metadata, not as document citations.\n- The structured peer set may lack a document-level source locator. Do not fabricate one; disclose that limitation when material.\n- Distinguish documented facts, management claims, and model interpretation.\n- A citation supports the nearby evidence, not a broader claim that the company has a durable or superior moat.\n- Do not provide trading instructions or personalized investment advice.\n"
}