Generate complete Looker Studio documentation following APPSHEET_SYSTEM_BLUEPRINT.md templates for data sources, calculated fields, metrics, dimensions, and blended data. Use when documenting Looker Studio reports, writing to docs/formulas/lookerstudio_formulas.md, or when user mentions Looker Studio, calculated fields, data sources, or report configurations.
Generate complete documentation templates for Looker Studio reports and data sources.
Automatic triggers (no user request needed):
docs/formulas/lookerstudio_formulas.mdManual invocation:
/lookerstudio-blueprint-skillExample triggers:
lookerstudio_formulas.md → Auto-apply blueprint formatThis skill provides complete documentation templates (see ):
Available Templates:
For complete templates with all fields, see TEMPLATES.md.
Determine what needs documentation:
Access the appropriate template from:
Include ALL required fields:
Check against requirements:
Connection:
Schema:
| Field Name | Type | Aggregation | Description |
|---|---|---|---|
| Date | Date | None | Transaction date |
| Product | Text | None | Product name |
| Revenue | Number | Sum | Sales amount |
| Quantity | Number | Sum | Items sold |
Data Freshness: Updates when report is opened Row Count: ~5,000 rows
Type: Metric Data Type: Number (Currency) Aggregation: Sum
Formula:
SUM(Revenue) - SUM(Cost)
**Purpose:** Calculate profit margin across all transactions
**Used In:** Profit Overview chart, Monthly Reports
**Dependencies:** Revenue, Cost fields
See TEMPLATES.md for complete templates with all fields.
SUM(Field)
Use Case: Total sum across all records
SUM(Field1) / SUM(Field2) * 100
Use Case: Percentage or rate calculation
CONCAT(CAST(YEAR(Date) AS TEXT), "-", CAST(MONTH(Date) AS TEXT))
Use Case: Group data by month or year
CASE
WHEN Status = "Active" THEN "Yes"
ELSE "No"
END
Use Case: Create derived categories
Looker Studio documentation MUST include:
For the complete Experimental→Stable promotion workflow, use /version-management-skill.
Looker Studio documentation files follow a 2-version discipline:
lookerstudio_formulas.md
├── EXPERIMENTAL V[X] (new data sources/fields being tested)
└── STABLE SYSTEM V[X-1] (current production)
Key Concepts:
backups/[date]-v[X]-stable/Starting new features:
Promoting to stable:
Use /version-management-skill which handles:
When promoting to stable:
✅ Looker Studio data source documentation ✅ Calculated field templates (metrics and dimensions) ✅ Blended data configuration ✅ Report and chart documentation ✅ Filter and control documentation
❌ Looker Studio UI help (use Looker Studio documentation) ❌ Chart design best practices (use Looker Studio resources) ❌ Data modeling architecture (use data engineering resources)
AUTOMATIC INVOCATION: When documenting any Looker Studio component, you MUST automatically use blueprint templates to ensure completeness.
Always use complete templates: Don't omit fields. Every data source needs connection details, schema, and refresh settings. Every calculated field needs type, formula, purpose, and dependencies.
Templates are in TEMPLATES.md: Use TEMPLATES.md as the source of truth for all documentation format templates.
For comprehensive templates and examples, see:
Version: 1.0 Last Updated: 2026-01-21 Source: lookerstudio-blueprint-skill/SKILL.md