Allen Houchins
b8e324383d
<!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** N/A # Checklist for submitter This PR only edits Claude Code skill files under `.claude/` — no product code, so most of the template below doesn't apply. ## What changed Documents the **build-enforced 150-character limit on `<meta name="description">`** in the content skills that generate that tag. `website/scripts/build-static-content.js:687` throws `An article page has an invalid description meta tag` and fails the entire production build for any page whose description exceeds 150 characters, regardless of category. Before this PR: - `fleet-article-formatting` never mentioned the limit at all. It had **no endmatter section whatsoever**, and `assets/article-template.md` shipped `<meta name="description" value="">` with no guidance in the placeholder. - `fleet-guide-formatting` and `content-style/references/content-types.md` stated "150 chars max" as what reads like a style preference, with no indication that going over breaks the deploy. So a draft could satisfy every skill self-check and still fail the build. Changes: - **`fleet-article-formatting/SKILL.md`** — new `### Endmatter` section covering the 150-char limit (naming the enforcing script and the error message), `articleTitle` matching the H1 exactly, and the no-fabrication rule for `authorFullName`/`authorGitHubUsername`/`publishedOn`. Added a matching self-check bullet. - **`fleet-article-formatting/assets/article-template.md`** — filled in the empty `description` placeholder with the constraint. - **`fleet-guide-formatting/SKILL.md`** — the two existing 150-char mentions now say build-enforced and name the failure mode. - **`content-style/references/content-types.md`** — same note on the shared endmatter block both skills point at, so it's stated once at the source. Each spot also says to **count** the characters rather than estimate, which is the actual failure mode: a description that reads like one or two natural sentences lands just over 150 more often than you'd expect. ## Why Found the hard way. A case study drafted in [#50152](https://github.com/fleetdm/fleet/pull/50152) had a 153-character description that read as perfectly reasonable length and broke `npm run build-for-prod`: ``` Error: Failed compiling markdown content: An article page has an invalid description meta tag (<meta name="description" value="Hawx automated seasonal iOS onboarding and offboarding with Fleet, Tines, and Okta, eliminating start-of-season helpdesk floods in a one-month migration.">) at ".../articles/hawx.md". To resolve, make sure the value of the meta description is less than 150 characters long. ``` The limit is cheap to respect while drafting and annoying to discover at deploy time, so it belongs in the skills that write the tag. ## Note for reviewers The proposed `fleet-case-study-formatting` skill in [#49917](https://github.com/fleetdm/fleet/pull/49917) is **not touched here**, deliberately, to avoid a conflict with that open PR. Its `assets/case-study-template.md` already says "150 chars max" in the description placeholder, though its `SKILL.md` doesn't mention the limit. Worth adding the build-enforcement note there before that PR merges, in that PR rather than this one. - [ ] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. — N/A, Claude Code config only, not a product change ## Testing - [ ] Added/updated automated tests — N/A, markdown/config only - [x] QA'd manually: - Traced the constraint to its source at `website/scripts/build-static-content.js:687` and confirmed the quoted error text and the `> 150` comparison, so the skills describe real behavior rather than a remembered rule. - Confirmed the check applies to all categories (it runs before the `category === 'case study'` branch), which is why the note went in the shared `content-types.md` block too. - Scanned every `<meta name="description">` across `articles/`, `docs/`, and `handbook/`: **0 pages currently exceed 150 characters**, so this is preventive documentation only and no existing content needs fixing. - Read the edited skill files back end-to-end for correct rendering and no contradictions with surrounding guidance.
News · Report a bug · Docs · Why open source? · Art
Open-source platform for IT and security teams with thousands of computers. Designed for APIs, GitOps, webhooks, YAML, and humans.
What's it for?
Fleet gives you a single system to secure and maintain all your computing devices over the air. You can do MDM, patch stuff, deploy software, and verify anything, all from one place, across every OS your organization uses.
Fleet works directly with data and events from the native operating system, down to the bare metal. Strong diagnostics let you investigate errors on end-user devices and collect accurate audit evidence in minutes.
Get started
You can try Fleet out for yourself, or grab time with one of the maintainers to chat.
Is it any good?
Fleet is used in production by IT and security teams managing thousands of devices. Many deployments support tens of thousands of hosts, and a few large organizations manage 400,000 or more.
Supported platforms
- Linux (all distros)
- macOS
- Windows
- Chromebooks
- iOS and Android (BYOD or corporate-owned)
- Amazon Web Services (AWS)
- Google Cloud (GCP)
- Azure (Microsoft cloud)
- Data centers
- Containers (kube, etc)
- Linux-based IoT devices
Infrastructure as code
Manage your fleet with GitOps, or use the GUI, REST API, webhook events, and the fleetctl command-line tool.
Linux support
First-class support for all major distros. Linux gets the same attention and visibility as macOS and Windows.
Visibility and compliance
Fleet can report on hundreds of attributes across your devices and ships with CIS benchmarks for macOS and Windows and comprehensive operating system, hardware, and software data. Check out the table reference documentation to see what's available.
Open by design
Fleet is open source and transparent about what it can and can't see. End users can verify exactly how the agent works and what data their company collects. Fleet collects only the data needed to manage and secure devices, not private activity like keystrokes, emails, or webcams.
Good neighbors
Ready-to-use, enterprise-friendly integrations exist for Snowflake, Splunk, GitHub Actions, Vanta, Elastic Jira, Zendesk, and more. Fleet also works with tools such as Munki, Chef, Puppet, Ansible, CrowdStrike, and SentinelOne.
Lighter than air
Fleet is lightweight and modular. You can use it for MDM without using it for security, and vice versa. You can turn off features you are not using.
Free as in free
The free version of Fleet will always be free. Fleet is independently backed and actively maintained with the help of many amazing contributors.
Longevity
The company behind Fleet is founded (and majority-owned) by true believers in open source. The company's business model is influenced by GitLab (NYSE: GTLB), with great investors, happy customers, and the capacity to become profitable at any time.
Fleet Device Management's company handbook is public and open source. You can read about the history of Fleet and our commitment to improving the product.
Chat
The Fleet community is full of kind and helpful people. Whether or not you are a paying customer, if you need help, just reach out.
Contributing 
Contributions are welcome, whether you answer questions on Slack / GitHub / LinkedIn, improve the documentation or website, write a tutorial, give a talk at a conference or local meetup, give an interview on a podcast, troubleshoot reported issues, or submit a patch. The Fleet code of conduct is on GitHub.
License
The free version of Fleet is available under the MIT license. The commercial license is also designed to allow contributions to paid features for users whose employment agreements allow them to contribute to open source projects. (See LICENSE.md for details.)
Fleet is built on osquery, nanoMDM, Nudge, and swiftDialog.