{"id":86326,"plugin_id":"plugin_asdk_app_697254461bb0819199d9f896114e1b98","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-09T00:21:25.971Z","digest":"4ab2c9232e9fae151e13423690d776f9197f256e1032b6fca9a870d33a64986a","against":null,"payload":{"description":"Use when the user requests company or project analytics based on verifiable sources, financial statements, useful charts, or a general 101 audit.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":43}],"name":"company-analytics","skill_md_contents":"---\nname: company-analytics\ndescription: Use when the user requests company or project analytics based on verifiable sources, financial statements, useful charts, or a general 101 audit.\nversion: \"2.2.0\"\nrole: primary\ninvocation: internal\nintents:\n  - analytics.company\n  - analytics.project\n  - analytics.report\ndepends_on:\n  - entity-resolution\nrequired_tools:\n  - whoami\n  - get_company_closing_balance\n  - list_projects\n  - list_events\n  - list_contractor_project_balances\noptional_tools:\n  - get_event\n  - get_company\n  - get_company_fund\n  - get_project_summary\n  - list_contractors\n  - list_project_members\n  - get_project_fund_settlements\n  - list_company_fund_projects\n  - list_company_fund_members\n  - list_company_fund_expenses_by_bill\n  - list_project_bill_balances\n  - list_project_estimate_positions\n  - list_bills\n  - list_tasks\n  - render_chart\n  - validate_artifact\n  - render_artifact\nresources:\n  - path: ../shared-resources/context-and-identity.md\n    kind: semantic-guide\n    required: true\n  - path: ../shared-resources/finance-and-balances.md\n    kind: semantic-guide\n    required: true\n  - path: ../shared-resources/safety-and-permissions.md\n    kind: semantic-guide\n    required: true\n  - path: ../shared-resources/technical-integrity-audit.md\n    kind: semantic-guide\n    required: true\n  - path: ../shared-resources/financial-risks-and-project-controls.md\n    kind: semantic-guide\n    required: true\n  - path: ../shared-resources/management-reporting-and-balances.md\n    kind: semantic-guide\n    required: true\ncompletion:\n  statuses:\n    - готово\n    - частично\n    - заблокировано\n---\n\n# Company and Project Analytics\n\nAnalyze verified data without changing the records. This workflow owns general audits, professional statements, and analytics with charts; return an ordinary list read to the dispatcher.\n\n## Mode\n\n- When the request only says “audit,” ask: “Should I check the entire company, a particular project, or a specific problem?” Do not ask again about a goal already known.\n- Cash flow statements, P&L/income statements, EBITDA, and the management balance cover projects and the company fund. P&L and income statement are the same report. Explain the same data more simply to a non-professional user.\n- Before a full company financial analysis, offer the optional technical check once. Reuse a known decision without asking again; a narrow request does not require it.\n- Agreement → `../shared-resources/technical-integrity-audit.md`, complete pagination, and the required details. Incompleteness or a failure of relationships, distributions, or arithmetic stops the full analysis; return the issues without correcting data.\n- Refusal → continue the analysis and state that integrity was not checked. Do not start the technical check without consent.\n\n## Data and meaning\n\n1. Use the resolved company; `whoami` and `entity-resolution` are needed when context is missing. Company details — `get_company`; fund — `get_company_fund`; project — `get_project_summary`.\n2. Settlement balance — `get_company_closing_balance`; portfolio — `list_projects`. Read only the aggregates needed for the goal, then details of material deviations.\n3. Event totals: `list_events`, `with_totals=true`, `per_page=0`, the exact company and period, and `status=[partner_verified, client_accepted]`. Calculate drafts separately. When an aggregate answers the question, do not read raw events. If the aggregate does not establish the metric, use the necessary records and details with an explicit completeness boundary; an agreed integrity check requires the complete set. A `list_events` aggregate by event date does not establish P&L for a confirmation period: confirmation/signature dates are needed. If they are unavailable, show a limited management analogue without calling it exact P&L.\n4. Time series: non-overlapping intervals, one aggregate per interval. Use the requested grain; otherwise, use up to 12 intervals with the coarsest suitable grain. Use the specified time zone, otherwise Europe/Moscow.\n5. Supplement `list_project_members` with `get_project_fund_settlements` for the same project. Signs, zeros, and incompleteness are covered in `../shared-resources/finance-and-balances.md`.\n6. Check risks using `../shared-resources/financial-risks-and-project-controls.md` and report formulas using `../shared-resources/management-reporting-and-balances.md`. Label an unprovable standard metric as a management analogue with its formula and limitation.\n\nProjects and the fund are separate scopes. A direct fund inflow is financing, not revenue or profit. Exclude internal project ↔ fund transfers from repeated income/expense on consolidation. Compare like units and periods; causality requires evidence.\n\n## Presentation\n\nAdd useful charts when the data supports them. “Text only,” “table only,” “data only,” and “no charts” restrict the format. State when presentation tools are unavailable and answer through an available method.\n\nDelegate formatting to `analytics-visualization`: a narrow question uses one `render_chart`; a broad audit uses one composite artifact through a successful `validate_artifact` and one `render_artifact` with unchanged data. Usefulness determines the chart count, not a quota. Sources, times, and safe filters come from actual calls, without GUIDs.\n\nAfter each chart: finding → meaning → a concrete recommendation for that signal. After the entire artifact: overall conclusion and company actions. Local and overall findings complement each other. Local formatting changes use loaded data; a new period or metric requires a new read and validation.\n\nLead with the answer and show key figures, facts, hypotheses, and limitations. Express amounts in rubles and understandable magnitudes; use “company owner.” Offer relevant deeper analysis. Follow `../shared-resources/safety-and-permissions.md`; do not describe a failed presentation as a displayed report.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}