🛠️ Agent Exercise 1: Convert Your Template to a SKILL.md

Create a steering file at .kiro/steering/anycompany-rules.md with these global rules for our AnyCompany Financial Group project: 1. All monetary amounts must be in SGD (Singapore Dollars) unless a specific market is referenced 2. Never include personally identifiable information (PII) in outputs — use [REDACTED] for names, account numbers, and contact details 3. Use AnyCompany Financial Group as the company name throughout 4. Southeast Asian market context: Singapore, Malaysia, Indonesia, Thailand, Vietnam, Philippines 5. All risk ratings must use the GREEN/AMBER/RED scale 6. When citing data, always reference the specific source field or document section 7. If data is missing or unavailable, state "DATA NOT AVAILABLE" rather than estimating Format it as a proper Kiro steering file with a front-matter section.

Create a Kiro skill at .kiro/skills/merchant-risk-assessment/SKILL.md Use this structure: - name: merchant-risk-assessment - description: Generate standardized merchant risk assessments with GREEN/AMBER/RED ratings. Use when reviewing merchant data, preparing risk committee reports, or evaluating merchant applications for AnyCompany Financial Group. For the skill content, use the prompt template I built in the Day 2 exercise. The template should include: - The Senior Risk Analyst persona - The 8-section structured output (Risk Rating, Executive Summary, Transaction Analysis, Chargeback Assessment, Complaint Analysis, Compliance Status, Recommended Actions, Monitoring Plan) - RAG grounding rules (ONLY use provided data) - Self-critique step - All {{variables}} for merchant data inputs Also add a "## When to Use" section listing the trigger scenarios: - New merchant onboarding review - Quarterly merchant portfolio assessment - Triggered by chargeback rate exceeding 1.0% threshold - Risk committee preparation And a "## Guardrails" section with: - Use ONLY provided merchant data - Do not reference external data sources - Flag [DATA NOT AVAILABLE] for missing metrics - Escalate to human review if risk rating is RED

Create a Kiro skill at .kiro/skills/credit-risk-narrative/SKILL.md Use this structure: - name: credit-risk-narrative - description: Convert quantitative credit model outputs (PD, LGD, DSCR) into plain-language narratives for credit committees. Use when preparing credit applications, PayLater limit reviews, or merchant financing assessments. For the skill content, use the prompt template I built in the Day 2 exercise. Include: - The Credit Committee Analyst persona - Structured output with APPROVE / APPROVE WITH CONDITIONS / DECLINE - Bull case and bear case analysis - All {{variables}} for credit model inputs Add "## When to Use" and "## Guardrails" sections similar to the merchant risk skill.

Create a Kiro hook that automatically runs the merchant risk assessment when new merchant data files are added to the project. The hook should: - Trigger when a CSV file is created in the workspace - Ask the agent to: "A new merchant data file was created. Use the merchant-risk-assessment skill to analyze this data and generate a risk assessment report. Save the output as a markdown file in the same directory with '_assessment' appended to the filename." Save it as a proper Kiro hook file.

I need to review a merchant for the risk committee. Here's the data: Merchant: QuickMart Express Pte Ltd (ID: MC-9921) Sector: Convenience retail, Singapore Monthly transactions: 2,100 → 8,400 (6-month trend) Average transaction: $12.30 SGD Chargeback rate: 0.4% → 3.2% (6-month trend) Complaints: 8 in last 30 days (up from 1) PayLater adoption: 45% of transactions Account age: 14 months Generate a full risk assessment.