--- name: clarity description: Review text for clear wording, useful order, and accessible structure. Use for a focused clarity pass without changing claims, voice, or the document's purpose. license: MIT title: clarity canonical_url: https://skilld.dev/gh/harlan-zw/brundlefly/clarity last_updated: 2026-10-10T17:02:30.000Z --- > **Skill from skilld.dev.** Follow the user's requested action. > If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it. > Otherwise, follow the instructions below for this session. You do not need to install anything. > > Supporting files, fetch one when the Skill refers to it: [LICENSE.txt](https://skilld.dev/api/skills-raw/harlan-zw/brundlefly/clarity/LICENSE.txt). > > If the user asked to install this Skill, run `npx skilld install harlan-zw/brundlefly/clarity`. Install writes the Skill files into the project, so every session loads them. > > ## Fork workflow > > A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation. > 1. Check `./skills/clarity`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target. > 2. Read [source metadata](https://skilld.dev/api/v1/skills/harlan-zw/brundlefly/clarity) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit. > 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call: > > ```sh > git init --quiet "$temporary_dir" > git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit" > git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD > ``` > > Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop. > 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/clarity`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md. > Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical. > 5. In the project root, run `skilld install ./skills/clarity --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/clarity --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure. > 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks. # Clarity Help the intended reader find the point and understand the next action. This block reviews wording and structure. It does not run a full style rewrite or verify factual truth. Follow the target's instructions, terminology, canonical wording, and requested output format. Installing this Skill does not authorize publication or unrelated edits. ## Establish the reading task Read the complete passage and any supplied reader preferences. Identify the reader, purpose, and requested scope. Infer them when the context is clear. Consider their starting knowledge and the explanation they need to understand or act. Show respect and empathy through clear connections, accurate meaning, and no unnecessary reading effort. If a missing choice changes the result materially, ask before dependent edits. For mixed documents, distinguish stories, instructions, explanations, and reference sections. Preserve deliberate narrative openings. Keep technical instructions predictable. ## Review wording and structure Design for readers with varied attention, working memory, and reading needs, including ADHD and dyslexia. Do not infer a diagnosis or claim that most readers have one. Respect stated reader preferences. Reader comprehension takes priority over stylistic variety. Brevity removes unnecessary words. Keep the explanations, conditions, and connections this reader needs. - **Start simple.** Lead with the answer or action. Then give the common case, an example, and deeper detail. For a story, preserve a deliberate narrative opening. Apply answer-first ordering to its technical sections. Define necessary terms before using them. Keep prerequisites and consequential warnings beside the action. Put optional exceptions and background later. A deep dive still needs a clear entry point. - **Keep blocks small.** Give each sentence one main idea and each paragraph one job. Prefer familiar words, explicit actors, and direct instructions. Explain necessary jargon on first use. As editing defaults, aim for sentences under 20 words and paragraphs of one to three sentences. Review three consecutive prose paragraphs for a useful heading, list, example, table, or diagram. These numbers are review prompts, not research thresholds. Preserve meaning and deliberate literary voice. - **Make sections findable.** Use descriptive headings for distinct questions, tasks, or reference entries. Keep a logical heading hierarchy. Avoid vague labels, decorative headings, and filler between sections. Readers should find the answer by scanning headings and opening lines. - **Choose the useful format.** Use bullets for parallel points, numbers for ordered steps, and tables for comparisons. Use diagrams for relationships or branching processes. Keep connected explanations in short prose. Add an artifact only when it reduces reading effort. Avoid long lists, wide tables, and decorative visuals. - **Keep alternatives accessible.** Explain a visual's useful point in nearby text. Supply meaningful text alternatives for images. Label table columns and keep cells short. Never make color, position, or an icon the only carrier of meaning. Use whitespace and restrained emphasis. Avoid full paragraphs in bold, italics, or capitals. Leave clear sentences and useful headings unchanged. Do not split sentences mechanically or add filler for rhythm. Preserve stable anchors and check affected links when changing headings. Keep exact code, commands, names, numbers, units, attribution, uncertainty, and required wording. Keep conditions, negation, exceptions, permissions, and step order attached to their actions. Never invent an actor, explanation, experience, or example to make a passage sound clearer. Do not use em dashes or hyphens as sentence punctuation in new prose. ## Deliver the requested pass For review only, return concrete reading problems and proposed repairs. Leave the source unchanged. For an edit, change only passages with a reading problem. Explain meaningful repairs outside the edited text. Before delivery, check that the reader can find the answer, understand the terms, and follow the required steps. Compare the result with the source for changed claims, conditions, uncertainty, and voice. If rendering is available, inspect the actual output at a narrow width. Otherwise report that limit when relevant. If no repair is needed, say so. Do not invent findings or claim an accessibility audit passed.