A writing guide for Sumo Logic documentation. It sets rules for tone, wording, and document checks.

Use it when drafting, editing, reviewing, or checking Sumo Logic documentation, including introductions, word choices, and front matter.

It helps keep documentation consistent and readable across the repository. It also provides a fallback when the live Sumo Logic style pages cannot be fetched.

How SumoLogic/sumologic-documentation configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to SumoLogic/sumologic-documentation. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/SumoLogic/sumologic-documentation/main/.claude/skills/sumo-style/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/SumoLogic/sumologic-documentation

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/sumologic/sumologic-documentation/sumo-style/github.svg)](https://agentmods.dev/skills/sumologic/sumologic-documentation/sumo-style)

Your own site

<a href="https://agentmods.dev/skills/sumologic/sumologic-documentation/sumo-style"><img src="https://agentmods.dev/badge/skills/sumologic/sumologic-documentation/sumo-style/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/sumologic/sumologic-documentation/sumo-style"><img src="https://agentmods.dev/badge/skills/sumologic/sumologic-documentation/sumo-style.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,939 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00055	$0.02939
Opus 5.5	$0.00022	$0.01176
Sonnet 5.5	$0.00011	$0.00588
Haiku 4.5	$0.00006	$0.00294

Measured 7d ago against content hash 885f9dad3c7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sumo-style scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/sumo-style/SKILL.md · 257 lines

How it starts

The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sumo Logic Style Guide

Always fetch before applying rules

Before writing, editing, or auditing any content, fetch both of these pages:

Apply the fetched rules. This is a living style guide -- the live pages take precedence over everything below. The rules below are fallback defaults only, for cases where the fetch fails or is unavailable.

Voice and tone

Address readers as "you". Never "the user" or "one."
Active voice. "Sumo Logic ingests data" not "data is ingested by Sumo Logic."
Conversational but professional. Avoid stiff, institutional language.
8th-grade reading level for introductory and instructional content.
No "please" in task directives. "Build the query using..." not "Please build..."
Use "need to" instead of "must" or "have to."
Always say "Sumo Logic" (not "Sumo" except in code); "we" is acceptable conversationally.
Avoid filler adjectives. Cut "very", "best", "simply", "just", "easy", "straightforward."
Be judicious with "always" and "never".

Contractions

Common contractions (you'll, they're, we're) are acceptable.
Negative contractions must be spelled out. "cannot" not "can't", "will not" not "won't", "do not" not "don't."
Avoid uncommon contractions. "should've", "it'll", "they'd" -- rewrite instead.

Language rules

No abbreviations. Write "for example" not "e.g.", "that is" not "i.e.", "and so on" not "etc."
Spell out acronyms on first use in body text: "Application Load Balancer (ALB)"; use ALB after. Do not spell out in headings.
No gender pronouns unless referring to a specific named person.
No regional idioms or slang.
Ampersand (&). Do not use for "and" in prose.
Numbers. Spell out one through nine; use numerals for 10 and above.

Inclusive language

Use	Avoid
allowlist	whitelist
denylist	blacklist
placeholder data	dummy data
primary / main	master
press / click	hit

Read the full file on GitHub · 257 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

7d ago Changed 885f9dad3c7c
8d ago Changed · +36 lines 84a4aba94a4b
23d ago Changed · +1 lines 7fe157e470fd
1mo ago Changed · -2 lines 12cef4cff2fe
2mo ago First seen · 222 lines · 55 tokens per session scan A d0ff691b84f8

Subscribe to this mod's changes

sumo-style is a skill published in the GitHub repository SumoLogic/sumologic-documentation (42 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 2,939 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

React Writing and docs documentation open-source

sumo-style next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
sumo-styleSumoLogic/sumologic-documentation	Skill	42	yesterday	MIT	A	55	Claude Code
reskinCopilotKit/CopilotKit	Skill	39k	yesterday	MIT	A	154	Claude Code
copilotkit-channelsCopilotKit/CopilotKit	Skill	39k	yesterday	MIT	A	112	Claude Code
setup-slack-channelCopilotKit/CopilotKit	Skill	39k	yesterday	MIT	A	206	Claude Code
channels-setupCopilotKit/CopilotKit	Skill	39k	yesterday	MIT	A	141	Claude Code
inspector-workbenchCopilotKit/CopilotKit	Skill	39k	yesterday	MIT	A	112	Claude Code
copilotkitCopilotKit/CopilotKit	Skill	39k	yesterday	MIT	A	104	Claude Code

sumologic-documentation: Skill for Claude Code