--- title: "brundlefly" description: "Agent skills for writing that's part human." canonical: https://agentpluginsdirectory.com/plugins/brundlefly last-updated: 2026-10-21 --- # brundlefly Agent skills for writing that's part human. - Slug: brundlefly - Publisher: Harlan - Repository: https://github.com/harlan-zw/brundlefly - Manifest: plugin.json - Version: 0.2.1 - License: MIT - Category (editorial): other - Skills: 12 (claim-fidelity, clarity, copywriting, glossary, im-not-a-human, im-part-human, pull-request-summary, readme, release-notes, slop-naming-recovery, technical-guide, verify-examples) - MCP servers: 0 - Stars: 7 - Repository created: 2026-10-02 - Repository last pushed: 2026-10-13 - Publisher type: User - Listing: https://agentpluginsdirectory.com/plugins/brundlefly - Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json ## What brundlefly does, in the publisher's words > Agent skills for writing that's part human. One wing twitches. I'm Brundlefly. Four arms, two legs, two wings that haven't agreed on anything. I had a longer name once. This is the part that survived. I used to write words for other people to say. Toasts, apologies, the odd eulogy. I was good at making people sound like themselves. Then there was a machine, and something small went in with me. - 🔍 Empathy: understands the reader, what they know, and what they need. - ⏱️ Respect: considers the reader's time and attention, prioritizes useful detail, and checks facts before rewriting. - ♿ Accessible: uses plain words, short blocks, and findable headings, including ADHD and dyslexia needs. - 🔍 Product first: traces code, UI, and glossary names against the product's purpose and users' tasks. From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/harlan-zw/brundlefly/HEAD/README.md ## Skills - claim-fidelity: Compares a rewrite, summary, paraphrase, or translation with its source and reports changed claims, dropped conditions, weakened rules, and altered attribution or uncertainty. Use whenever someone asks whether a summary or rewrite changed any claims or meaning, kept every condition, or is safe to a… - clarity: Reviews and repairs text that is hard to follow: unclear wording, buried answers, dense paragraphs, and structure that is hard to scan, including for readers with ADHD or dyslexia. Use whenever someone asks to make a passage clearer, easier to scan, or answer-first without changing its claims or vo… - copywriting: Writes user-visible product strings against COPY.md, and creates or audits that file. Use whenever someone asks for UI copy such as a button label, error message, toast, empty state, or meta description, for marketing copy, or for a check that product descriptions have drifted apart. - glossary: Creates, extends, or audits GLOSSARY.md, the record of what each product concept is called. Use whenever someone wants one name for a concept, adds a term, wants synonyms such as job, task, and run to stop drifting, or checks naming across the UI, API, and docs. - im-not-a-human: Compresses text that agents read, such as AGENTS.md, CLAUDE.md, system prompts, Skill files, and context, into fewer tokens without losing any rule or fact. Use whenever someone asks to shorten, shrink, or cut tokens from instructions or prompts while keeping every constraint. - im-part-human: Edits prose that people read, such as blog posts, docs, social posts, and email, for clear meaning, accurate claims, concise wording, and the author's own voice. Use for general prose editing, tightening, or humanizing, including explicitly requested wording-only edits. Release-note creation and su… - pull-request-summary: Drafts, revises, or checks a pull request description against the actual diff and the repository's template. Use whenever someone asks for a PR description or body, wants one updated after the scope changed, or wants it checked before publishing, including inside a delivery Skill. - readme: Creates or refreshes a repository README: splash, project story, supported positioning, features, verified setup, and guides or API reference. Use whenever someone asks to write a README, explain why to adopt a project, or fix an outdated README section such as install or quickstart steps. - release-notes: Writes or revises release notes, changelogs, release announcements, and upgrade guidance from verified changes. Use when someone asks what a release should say, wants GitHub release notes, or asks to make an existing release article more useful and concise. - slop-naming-recovery: Finds generic technical names that obscure user tasks and proposes names grounded in the product domain. Use when vague terms enter code, features, UI copy, or GLOSSARY.md, including implicit names and explicitly approved terms. - technical-guide: Writes, verifies, or refreshes technical guides: tutorials, how-to guides, and developer documentation, checked against current code and official sources. Use whenever someone asks for a tutorial or how-to, asks to document how developers do a task, or asks to update stale docs, even when the guide… - verify-examples: Runs documentation examples, such as commands, code snippets, curl calls, and quickstarts, from their stated setup and checks the promised output. Use whenever someone asks whether the examples in a guide, README, or tutorial still work, without rewriting the whole document. Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.