{"id":9781,"plugin_id":"plugin_asdk_app_6a7762af20c881919eadbba72de11a09","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T22:55:39.538Z","digest":"fc06f479424b3e76976eb45c9ddcfdca5f2dfcfd66de7a77abc3d16d3f7a6b03","against":null,"payload":{"name":"revenue-segmentation","description":"Extract reported revenue segments from company documents.","included_files":[],"skill_md_contents":"---\nname: revenue-segmentation\ndescription: Extract reported revenue segments from company documents.\n---\n\n# Reported Revenue Segmentation\n\nUse this skill when a user asks for revenue by geography, business segment, industry vertical, or another dimension reported in an Indian listed company's documents.\n\n## Internal workflow\n\n1. Resolve one company with `search_companies`.\n2. Use `list_document_availability` to identify relevant annual reports, presentations, results, transcripts, or company updates for the requested periods.\n3. Inspect `complete_result`, `truncated`, and `truncation_policy`. Never treat a truncated inventory as exhaustive.\n4. Search one bounded fiscal period and relevant document types at a time with `search_company_documents`.\n5. Inspect cited segment-reporting passages and tables with `get_document_chunks`.\n6. Extract only values explicitly present in the retrieved evidence. Preserve the company's exact segment names, period, currency, unit, consolidated or standalone scope, continuing or discontinued operations, and any restatement note.\n7. Treat the resulting table as model-derived from cited company-document passages, not as a structured segmentation dataset.\n8. Do not combine renamed, regrouped, or differently defined segments without explaining the mismatch.\n9. Prefer company-reported percentages. Calculate a share or change only when every operand is present in cited evidence. Show the formula and label the result as calculated from reported figures.\n10. Never interpolate missing periods, backfill unavailable values, derive an undisclosed residual, or calculate a mix shift from incomplete operands.\n11. When periods are not comparable, present them separately and explain why.\n\n## Public answer\n\nUse these sections:\n\n1. **Reported segmentation table**.\n2. **Observed changes** — only source-stated or transparently calculated changes.\n3. **Comparability notes** — definitions, units, basis, restatements, and missing periods.\n4. **Coverage limitations** — unavailable or truncated document inventory.\n5. **Sources**.\n\nSuggested table:\n\n| Period | Reported segment | Reported revenue | Share of total | Reporting basis | Source |\n|---|---|---:|---:|---|---|\n\nDo not require a document title when the returned evidence does not supply one. A citation may use the returned document type, fiscal period, page, and URL.\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, document identifiers, schemas, or retrieval narration in the public answer.\n- Use only returned document URLs, fiscal periods, document types, and page numbers. Do not invent titles or repair missing links.\n- Attach citations to each reported figure or tightly grouped set of figures from the same passage.\n- Label calculations as model calculations; citations support their inputs, not the calculation itself.\n- State when the available evidence does not support a requested total, trend, or comparison.\n- Do not provide trading instructions or personalized investment advice.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}