Corporate Brand Document Standards
Standardize generated presentations, spreadsheets, and PDFs around a consistent corporate brand system.
The code mainly returns configuration dictionaries and shows no network access, credential handling, or destructive external actions, so no red-line risk is evident. However, it lacks permission boundaries, user confirmation, data-flow disclosure, rollback guidance, and sensitive-data handling; the referenced logo path is also not supplied, so points are deducted.
The three formatting paths and validation helpers are broadly internally consistent, and unsupported document types raise a clear exception. However, there are no tests for key paths, little handling for malformed inputs or missing fields, and fragile parsing logic such as font detection. Under static calibration, the score cannot exceed 10.
The intended scenarios, supported Excel/PowerPoint/PDF configuration types, and many formatting rules are reasonably clear. However, the implementation returns configurations rather than finished documents, hardcodes Acme Corporation as a placeholder brand, and does not define trigger conditions, non-fit boundaries, Chinese-language layout, or mainland-China environment support.
The SKILL.md, REFERENCE.md, and scripts are readable and layered, with examples, limitation notes, a license, and partial version history. Installation and dependency instructions, the actual logo asset, API stability guidance, a changelog, and explicit maintenance ownership are missing; the repository README also does not align with this brand skill.
The scripts can produce formatting configurations for three document types and provide color, number, and content validation, giving them limited practical value. They do not create or modify actual Excel, presentation, or PDF files, and templates and the logo are not implemented, leaving substantial integration and review work.
The source code, documentation, and examples are auditable primary material, and interfaces can be reasoned about from the files. There are no skill-specific tests, CI coverage, or third-party execution results, so actual output cannot be confirmed statically and the score is capped at 5.
- The skill hardcodes Acme Corporation and its brand assets, so applying it to another organization may produce incorrect or misleading branding.
- apply_brand.py returns configuration dictionaries rather than rendering files, and assets/acme_logo.png is not present in the supplied materials.
- No skill-specific tests or reproducible execution evidence are provided; users should validate library integration, input boundaries, and generated files before adoption.
- Color and font validation have parsing limitations and do not cover Chinese fonts, pagination, accessibility, or complex templates.
What it does & when to use it
This skill defines a unified visual and editorial system for documents created for Acme Corporation. It covers colors, typography, layouts, logo placement, tone of voice, data formatting, and quality checks for PowerPoint, Excel, and PDF documents. It also lists two Python scripts, but does not explain how to run them. The guidance is detailed for Acme’s example brand and may require adaptation for another organization.
Applies Acme’s specified blue, navy, white, and secondary colors; sets Segoe UI and related fallback fonts with heading hierarchies; defines PowerPoint title, divider, content, and data slide structures; specifies Excel headers, data cells, borders, alternating rows, and chart defaults; specifies PDF headers, footers, margins, spacing, and heading styles; guides professional, clear, active, and positive messaging; and provides a final review checklist covering logo placement, colors, fonts, spelling, data accuracy, and professional tone. The file names apply_brand.py and validate_brand.py are listed, but their invocation is undocumented.
- A corporate team preparing an external PowerPoint presentation that needs consistent title slides, charts, layouts, and brand colors.
- A finance or operations user building an Excel report that needs standardized headers, borders, alternating rows, and chart colors.
- A documentation team producing a PDF report or notice with consistent headers, footers, margins, and heading levels.
- A marketing or brand team that wants generated copy to use formal, clear, active, and positive language.
- A team performing a pre-publication review of generated documents against a defined corporate identity.
Pros & cons
- Covers three common document formats: PowerPoint, Excel, and PDF.
- Provides concrete color, font, size, margin, and layout specifications.
- Includes guidance for tone, standard phrases, number formatting, tables, and charts.
- Includes a practical finalization checklist for brand compliance.
- The example identity is specific to Acme Corporation and must be rewritten for other organizations.
- It requires a company logo but provides no logo asset or insertion procedure.
- The usage and dependencies of apply_brand.py and validate_brand.py are not documented.
- No test suite, supported-platform list, or rendered output examples are provided.
- Exceptions for internal documents and special projects are described only at a high level.
How to install
The skill is located at skills/custom_skills/applying-brand-guidelines/SKILL.md in the repository. The supplied material provides no standalone installation command or procedure; place the skill directory in the skills directory of an Agent Skills-compatible client.
How to use
After loading the skill in a compatible environment, give it a concrete document request, such as: “Create a PowerPoint presentation following Acme Corporation’s brand guidelines, using Acme Blue and Segoe UI and applying the required title-slide and chart rules.” The source does not document a specific command, parameter set, or API.