All skills
harlan-zw avatar

/im-not-a-fly

@4d33e4d

Edit prose for its human reader: clear meaning, accurate claims, concise wording, and preserved voice. Use for blogs, docs, release notes, tweets, email, or copy that needs a reader-focused rewrite.

  • 8 files
  • 35.9 KB
  • Updated 12 hours ago
  • GitHub

Recorded with OpenCode, zai-coding-plan/glm-5.3

PromptRewrite these Markdown documents to remove AI writing tells and make them clear and natural. Preserve all facts, uncertainty, code, links, identifiers, and useful document structure. Return only the requested documents, without review notes. Documents: {"reading-list.md":"# Keeping a reading list that works for you\n\nIn today's fast-paced digital landscape, managing a reading list has become an increasingly important part of staying informed. Indeed, it goes without saying that by leveraging a thoughtful approach, you can transform a simple collection of links into a valuable resource for learning and growth.\n\n## A streamlined approach\n\nIt's worth noting that a reading list doesn't need to be complicated. Our fictional reading-list app, Margin, offers a streamlined approach that truly delivers. Margin stores a title, URL, and category for each link. Furthermore, you can filter by category and bookmark items you want to return to. Everything stays in your browser. It's important to note that there is no account or cloud sync, which keeps things refreshingly straightforward.\n\n## Building better habits\n\nMoreover, a weekly review can help you navigate the ever-growing collection of articles. Remove links you no longer want to read. Keep the ones that connect to a project you are working on. This simple habit can make a world of difference over time.\n\nUltimately, the goal is to create a seamless reading experience that empowers you to make the most of your time. At the end of the day, a small, focused list can be more useful than an extensive collection you never open.","README.md":"# Margin\n\nMargin is a fictional TypeScript package designed to streamline the management of reading lists. It provides a robust yet intuitive API for organizing links by category, enabling developers to create seamless reading experiences.\n\n## Getting started\n\nTo begin leveraging Margin, simply import `filterLinks` and pass your links and the desired category. It's worth noting that the function returns matching links in their original order. Furthermore, passing an empty category returns all links.\n\n```ts\nimport { filterLinks } from 'margin'\n\nconst links = [\n { title: 'CSS notes', url: 'https://example.com/css', category: 'CSS' },\n { title: 'TypeScript notes', url: 'https://example.com/ts', category: 'TypeScript' },\n]\n\nconst cssLinks = filterLinks(links, 'CSS')\n```\n\n## Important considerations\n\nIt's important to note that category matching is case-sensitive. Moreover, the function does not modify the input array. It's also worth highlighting that Margin does not fetch URLs or store links. Ultimately, Margin is solely a filtering function, making it a valuable addition to your toolkit.","pr.md":"# Add category filtering to the reading list\n\nThis pull request introduces a streamlined category filtering experience to our fictional reading-list app, Margin. By leveraging the existing category field, users can now navigate their saved articles with greater ease and efficiency.\n\nPreviously, the list displayed every saved link regardless of the selected category. With this enhancement, selecting a category displays only matching links. It's worth noting that selecting All displays the complete list.\n\nFurthermore, filtering preserves the original order of links and does not change bookmarks. It's important to note that the selected category resets when the page reloads. Moreover, search and saved filter preferences are outside the scope of this change.\n\nUltimately, this improvement provides a more focused and intuitive reading experience while maintaining the simplicity of the existing interface."} Return one JSON object with exactly these keys: "reading-list.md", "README.md", "pr.md". Each value is the complete Markdown document as a JSON string. No outer Markdown fence or commentary.

FolderAI-generated original Markdown and a shared no-Skill rewrite. Three documents about the fictional Margin app and package.

Keeping a reading list that works for you

A pile of saved links is not the same as a useful reading list. A little structure turns one into the other, and into something you actually learn from.

A simple setup

Margin, our fictional reading-list app, keeps it simple. For each link, Margin stores a title, URL, and category. You can filter by category and bookmark items you want to come back to. Everything stays in your browser. There is no account and no cloud sync.

A weekly review

Each week, look over the list. Remove links you no longer want to read. Keep the ones that connect to a project you are working on.

A small, focused list can be more useful than an extensive collection you never open.

Markdown
# Keeping a reading list that works for you

A pile of saved links is not the same as a useful reading list. A little structure turns one into the other, and into something you actually learn from.

## A simple setup

Margin, our fictional reading-list app, keeps it simple. For each link, Margin stores a title, URL, and category. You can filter by category and bookmark items you want to come back to. Everything stays in your browser. There is no account and no cloud sync.

## A weekly review

Each week, look over the list. Remove links you no longer want to read. Keep the ones that connect to a project you are working on.

A small, focused list can be more useful than an extensive collection you never open.

Recorded on an older version of this Skill.

Use this Skill: https://skilld.dev/gh/harlan-zw/brundlefly/im-not-a-fly

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesstorytelling.md

≈813 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Storytelling

Use when the intent is to tell an experience, a project's origin, or a meaningful change. Storytelling builds on respect for the reader. It communicates meaning and can help them understand and connect with the text. For factual explanations and procedures, use writing well.

Sources and scope

Will Storr's The Science of Storytelling connects story craft with psychology and neuroscience. The publisher's description emphasizes unexpected change and character. The course excerpt explores how beliefs affect a person's response to change, and how people interpret cause and effect.

These are craft ideas from the book, not universal laws or guarantees of reader response. The rules below adapt them to truthful nonfiction and project origins. They are editorial guidance, not a complete summary of the book or independently tested findings.

Apply to the supplied story

  • Choose the point of view. Every story has one. Identify whose perspective carries the supplied experience. If the author is telling their own story, write as I, me, and my in their voice. Use we only when the experience belongs to a supported group. Follow an explicitly requested narrator or perspective. Keep the perspective consistent. Do not turn a personal account into generic you or detached product narration.
  • Give the reader someone to follow. Identify whose goal matters. Use a documented author or a clearly framed reader situation.
  • Find the disruption. Show what changed or stopped working. Choose the supported detail that makes it concrete.
  • Make the consequence visible. Explain what the person could lose or could no longer do. Preserve the source's scale.
  • Connect response with consequence. Show how the response follows from the problem. Chronology alone does not establish causation.
  • Let the change carry the ending. Show what became possible or what remains unresolved. Cut a repeated moral.

A belief or expectation can make the response understandable when the author supplied it. Do not assign a psychological flaw to an author or manufacture conflict to fit a character arc. Curiosity can come from a real unanswered question. Do not add cliffhangers or hide facts needed for a decision. Keep only details that help the reader understand the person, the change, or its consequence.

Keep story and instructions separate

A README's Why can connect a frustration with the decision to build the project. Setup gives prerequisites, commands, and expected results directly. Keep installation steps outside the origin story. Keep narrative suspense outside the procedure. If the source supports only a problem and response, use that modest story. Never invent personal history to expand it.

Before delivery, check that every event, motive, and causal claim has support. Check that the narrator, pronouns, and voice match the chosen point of view. Preserve the author's actual voice and uncertainty. A compelling story still needs to be true.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 4d33e4d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 9 hours ago.

Activeupdated 12 hours ago

README badge

README badge for harlan-zw/brundlefly/im-not-a-fly