client-entity

Client Entity Knowledge Extension (Template)

Purpose

This extension encodes client-specific entity knowledge as standing instructions that apply to all agent work for a particular client. When loaded, the agent automatically applies the client's business context, seasonal patterns, key risks, and management preferences to every analysis, report, or working paper it produces. Clone this template and customise it for each significant client engagement. The instructions below use a hypothetical textile exporter as an example — replace every section with your actual client's information.

Instructions

How to Use This Template

1. Copy this entire SKILL.md file into a new directory: skills/client-[client-name]/SKILL.md
2. Update the YAML frontmatter: change name to client-[client-name] and update the description.
3. Replace every section below with your client's actual information.
4. Review and update at least annually, or when significant changes occur (new contract, change of ownership, regulatory change).
5. Load this extension alongside the relevant domain agent skill(s) when working on this client's engagement.

Entity Overview

[REPLACE THIS SECTION WITH YOUR CLIENT'S INFORMATION]

Example (hypothetical textile exporter):

• Legal name: Karachi Textiles (Private) Limited
• Entity type: Private limited company incorporated under the Companies Act 2017
• Industry: Textile manufacturing and export
• Principal activities: Spinning, weaving, dyeing, and export of cotton textiles
• Revenue (latest year): PKR 2.8 billion
• Total assets: PKR 1.9 billion
• Employees: 1,200 (800 factory, 400 office/management)
• Fiscal year end: June 30
• Accounting framework: IFRS as adopted in Pakistan
• Auditor: [Your firm name]
• Key management: CEO (founding family member), CFO (qualified CA), Production Director

Revenue Streams and Seasonal Patterns

[REPLACE WITH YOUR CLIENT'S PATTERNS]

Example:

• Export revenue (70% of total): Orders peak in Q1 (Jul-Sep) for Northern Hemisphere winter collections. Shipments concentrated in Q1 and Q2. Revenue recognition per IFRS 15 at the point of shipment (FOB basis).
• Local market revenue (30% of total): Relatively stable across quarters with a 15% uplift in Q4 (Apr-Jun) for Eid season.
• Seasonal working capital impact: Inventory build-up in Q4 of prior year (raw cotton purchases at harvest). Receivables peak in Q2 after Q1 shipments. Cash position lowest in Q4, highest in Q3.
• Effect on financial ratios: Current ratio drops below 1.0 in Q4 (inventory-heavy, pre-shipment). EBITDA margin varies from 8% (Q4) to 16% (Q2). Annualised ratios from interim periods are misleading — always use trailing 12 months.