{
  "name": "FAi Brilliance",
  "description": "FieldAssist skill registry — reusable SKILL.md standards that make every output consistent, on-brand, and world-class by default.",
  "homepage": "https://fai-brilliance.netlify.app",
  "updatedAt": "2026-07-14T10:59:50.529Z",
  "skills": [
    {
      "id": "master-fieldassist-format",
      "name": "Follow the FieldAssist Format",
      "description": "The master standard — aligned to the 2026 FieldAssist Brand & Identity Guidelines. Logo, colours, Poppins typography, voice, and structure that every output inherits. Read this first.",
      "department": "All",
      "category": "Doc",
      "tier": "certified",
      "isMaster": true,
      "author": "Brilliance Core Team",
      "version": "4.1.0",
      "tags": [
        "brand",
        "master",
        "standard",
        "identity",
        "logo",
        "poppins",
        "style"
      ],
      "file": "r/master-fieldassist-format.md"
    },
    {
      "id": "mbr-deck-standard",
      "name": "MBR Deck Standard",
      "description": "The certified structure for Monthly Business Review decks — slide order, KPI framing, and the narrative arc from performance to actions.",
      "department": "CST",
      "category": "PPT",
      "tier": "certified",
      "isMaster": false,
      "author": "CST Delivery Guild",
      "version": "2.1.0",
      "tags": [
        "mbr",
        "deck",
        "review",
        "kpi",
        "cst"
      ],
      "file": "r/mbr-deck-standard.md"
    },
    {
      "id": "ro-output-format",
      "name": "RO Output Format",
      "description": "Certified layout for Retailing Operations (RO) output workbooks — sheet order, column conventions, and the summary tab clients actually read.",
      "department": "CST",
      "category": "Excel",
      "tier": "certified",
      "isMaster": false,
      "author": "CST Data Team",
      "version": "1.8.0",
      "tags": [
        "excel",
        "ro",
        "tracker",
        "data",
        "cst"
      ],
      "file": "r/ro-output-format.md"
    },
    {
      "id": "client-email-standard",
      "name": "Client Email Standard",
      "description": "Certified format for external client emails — subject-line pattern, the 3-part body, and a tone that reads unmistakably FieldAssist.",
      "department": "Sales",
      "category": "Email",
      "tier": "certified",
      "isMaster": false,
      "author": "Sales Enablement",
      "version": "1.4.0",
      "tags": [
        "email",
        "client",
        "communication",
        "sales",
        "doc"
      ],
      "file": "r/client-email-standard.md"
    },
    {
      "id": "qbr-commentary-guide",
      "name": "QBR Commentary Guide",
      "description": "Certified approach to Quarterly Business Review commentary — how to turn a quarter of data into a defensible narrative with clear recommendations.",
      "department": "CST",
      "category": "Consultative",
      "tier": "certified",
      "isMaster": false,
      "author": "Consulting Practice",
      "version": "2.0.0",
      "tags": [
        "qbr",
        "commentary",
        "analysis",
        "narrative",
        "consultative"
      ],
      "file": "r/qbr-commentary-guide.md"
    },
    {
      "id": "sales-pipeline-tracker",
      "name": "Sales Pipeline Tracker",
      "description": "A lightweight, opinionated pipeline sheet — stages, weighted forecast, and a hygiene checklist so the numbers stay trustworthy.",
      "department": "Sales",
      "category": "Excel",
      "tier": "community",
      "isMaster": false,
      "author": "Priya N.",
      "version": "1.2.0",
      "tags": [
        "pipeline",
        "forecast",
        "sales",
        "excel",
        "crm"
      ],
      "file": "r/sales-pipeline-tracker.md"
    },
    {
      "id": "release-notes-template",
      "name": "Release Notes Template",
      "description": "Customer-facing release notes that are actually read — grouped by impact, written in benefit-first language, with a consistent changelog spine.",
      "department": "P&C",
      "category": "Doc",
      "tier": "community",
      "isMaster": false,
      "author": "Rahul M.",
      "version": "1.1.0",
      "tags": [
        "release",
        "changelog",
        "product",
        "doc",
        "p&c"
      ],
      "file": "r/release-notes-template.md"
    },
    {
      "id": "win-loss-analysis",
      "name": "Win-Loss Analysis",
      "description": "A structured way to dissect why deals are won or lost — evidence-based themes, not anecdotes, ending in one changeable action.",
      "department": "Sales",
      "category": "Consultative",
      "tier": "community",
      "isMaster": false,
      "author": "Sandeep K.",
      "version": "1.0.0",
      "tags": [
        "win-loss",
        "deals",
        "analysis",
        "sales",
        "consultative"
      ],
      "file": "r/win-loss-analysis.md"
    },
    {
      "id": "onboarding-deck",
      "name": "Client Onboarding Deck",
      "description": "The first deck a new client sees — sets expectations, the 30/60/90 plan, and who to call, all in the FieldAssist voice.",
      "department": "P&C",
      "category": "PPT",
      "tier": "community",
      "isMaster": false,
      "author": "Meghna R.",
      "version": "1.3.0",
      "tags": [
        "onboarding",
        "deck",
        "kickoff",
        "p&c",
        "ppt"
      ],
      "file": "r/onboarding-deck.md"
    },
    {
      "id": "data-cleanup-playbook",
      "name": "Data Cleanup Playbook",
      "description": "A repeatable checklist to take a messy export to analysis-ready — dedupe, type-fix, and validate, with the checks that catch silent errors.",
      "department": "CST",
      "category": "Excel",
      "tier": "community",
      "isMaster": false,
      "author": "Arjun T.",
      "version": "1.0.0",
      "tags": [
        "data",
        "cleanup",
        "excel",
        "quality",
        "cst"
      ],
      "file": "r/data-cleanup-playbook.md"
    },
    {
      "id": "mom-standard",
      "name": "Minutes of Meeting (MoM)",
      "description": "Minutes that drive action — decisions, owners, and dates captured in a scannable format people actually follow up on.",
      "department": "All",
      "category": "Doc",
      "tier": "community",
      "isMaster": false,
      "author": "Nisha P.",
      "version": "1.1.0",
      "tags": [
        "mom",
        "minutes",
        "meeting",
        "actions",
        "doc"
      ],
      "file": "r/mom-standard.md"
    },
    {
      "id": "retention-insight-brief",
      "name": "Retention Insight Brief",
      "description": "A one-page brief that explains a churn or retention signal and recommends the intervention — evidence in, decision out.",
      "department": "P&C",
      "category": "Consultative",
      "tier": "community",
      "isMaster": false,
      "author": "Vikram S.",
      "version": "1.0.0",
      "tags": [
        "retention",
        "churn",
        "brief",
        "analysis",
        "consultative"
      ],
      "file": "r/retention-insight-brief.md"
    },
    {
      "id": "api-design-standard",
      "name": "API Design Standard",
      "description": "The certified way FieldAssist designs REST APIs — resource naming, versioning, status codes, errors, and pagination, so every service feels like one.",
      "department": "Tech",
      "category": "Code",
      "tier": "certified",
      "isMaster": false,
      "author": "Platform Engineering",
      "version": "1.3.0",
      "tags": [
        "api",
        "rest",
        "backend",
        "code",
        "tech"
      ],
      "file": "r/api-design-standard.md"
    },
    {
      "id": "code-review-checklist",
      "name": "Code Review Checklist",
      "description": "What to actually look for in a pull request — correctness, tests, security, and readability — plus how to give feedback that lands.",
      "department": "Tech",
      "category": "Code",
      "tier": "community",
      "isMaster": false,
      "author": "Aditya R.",
      "version": "1.1.0",
      "tags": [
        "code-review",
        "pr",
        "quality",
        "tech",
        "code"
      ],
      "file": "r/code-review-checklist.md"
    },
    {
      "id": "release-sop",
      "name": "Release SOP",
      "description": "The step-by-step runbook for shipping a release safely — pre-flight checks, deploy, verify, and rollback — so releases are boring.",
      "department": "Tech",
      "category": "SOP",
      "tier": "community",
      "isMaster": false,
      "author": "DevOps Guild",
      "version": "1.0.0",
      "tags": [
        "release",
        "deploy",
        "sop",
        "runbook",
        "tech"
      ],
      "file": "r/release-sop.md"
    },
    {
      "id": "social-post-standard",
      "name": "Social Post Standard",
      "description": "On-brand social posts (LinkedIn-first) — the hook, structure, and visual rules that make FieldAssist instantly recognizable in a feed.",
      "department": "Marketing",
      "category": "Design",
      "tier": "community",
      "isMaster": false,
      "author": "Brand & Comms",
      "version": "1.2.0",
      "tags": [
        "social",
        "linkedin",
        "design",
        "marketing",
        "brand"
      ],
      "file": "r/social-post-standard.md"
    },
    {
      "id": "campaign-brief-standard",
      "name": "Campaign Brief",
      "description": "A one-page marketing brief that aligns everyone before work starts — objective, audience, message, channels, and how success is measured.",
      "department": "Marketing",
      "category": "Doc",
      "tier": "community",
      "isMaster": false,
      "author": "Growth Marketing",
      "version": "1.0.0",
      "tags": [
        "campaign",
        "brief",
        "marketing",
        "planning",
        "doc"
      ],
      "file": "r/campaign-brief-standard.md"
    },
    {
      "id": "hr-onboarding-sop",
      "name": "HR Onboarding SOP",
      "description": "The first-two-weeks playbook for a new hire — pre-boarding, day one, and week one — so everyone gets a consistent, warm start.",
      "department": "HR",
      "category": "SOP",
      "tier": "community",
      "isMaster": false,
      "author": "People & Culture",
      "version": "1.1.0",
      "tags": [
        "hr",
        "onboarding",
        "sop",
        "people",
        "process"
      ],
      "file": "r/hr-onboarding-sop.md"
    },
    {
      "id": "board-update-standard",
      "name": "Board & Investor Update",
      "description": "The certified monthly board/investor update — TL;DR, metrics, wins, lowlights, and asks — that builds trust through candor and consistency.",
      "department": "Founders Office",
      "category": "Doc",
      "tier": "certified",
      "isMaster": false,
      "author": "Founders Office",
      "version": "2.0.0",
      "tags": [
        "board",
        "investor",
        "update",
        "founders",
        "doc"
      ],
      "file": "r/board-update-standard.md"
    },
    {
      "id": "qa-test-case-standard",
      "name": "QA Test Case Standard",
      "description": "How to write test cases that anyone can run and that actually catch regressions — clear steps, expected results, and coverage of the unhappy paths.",
      "department": "QA",
      "category": "SOP",
      "tier": "community",
      "isMaster": false,
      "author": "Quality Assurance",
      "version": "1.0.0",
      "tags": [
        "qa",
        "testing",
        "test-case",
        "sop",
        "quality"
      ],
      "file": "r/qa-test-case-standard.md"
    },
    {
      "id": "exec-kpi-dashboard",
      "name": "Exec KPI Dashboard",
      "description": "A one-screen executive dashboard standard — the metrics that belong, the layout, and the rule that every number links to an action.",
      "department": "CST",
      "category": "Dashboard",
      "tier": "community",
      "isMaster": false,
      "author": "Analytics Team",
      "version": "1.1.0",
      "tags": [
        "dashboard",
        "kpi",
        "bi",
        "exec",
        "analytics"
      ],
      "file": "r/exec-kpi-dashboard.md"
    }
  ]
}