agentleFS
nexmoenexmoe/VidBee/skills/article-rewrite/SKILL.md

article-rewrite

Skill11k starsChanged 48 days agoMITView on GitHub

Rewrite source material as a complete article, adding relevant video stills when available. Use to turn a recording into publishable prose.

Trending

Less talk lately.about the whole repository

Dec 2025: 3 mentionsJan 2026: 4 mentionsFeb 2026: 0 mentionsMar 2026: 2 mentionsApr 2026: 1 mentionMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 2 mentionsAug 2026: 2 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the nexmoe/VidBee repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about nexmoe/VidBee

The biggest 5 of 17 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 17

Talked about on Bluesky, YouTube, GitHub and the web (17 times).

On Bluesky · 12

7 more on Bluesky

On YouTube · 3

On GitHub · 1

On the web · 1

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the supplied source evidence directly.

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Article rewriting

Use this when the user wants a rewrite or illustrated article. Match the requested scope and level of detail. Full article rewrites include relevant source video screenshots by default, unless the user asks for text only or source metadata says mediaKind is audio / hasVideoFrames is false. If the source is audio-only, skip capture_frames and write a text-only article. Illustrations should fit the written content; there is no limit. This default does not apply to quick summaries or ordinary follow-up questions.

  1. Use the supplied source evidence directly. Retrieve missing context with read_transcript; document mode is useful for broad reading. Follow pagination cursors when more source is needed.
  2. If hasVideoFrames is true, use capture_frames whenever an illustration helps: while exploring the source, drafting a section, or refining the article. Choose the number and placement from the content and the user's needs, with no fixed minimum, maximum or per-section quota. Existing screenshots are reusable material, not the complete set of available illustrations. Section writers can capture and inspect additional frames after handing off to write_article. Use original subtitle cues to locate relevant moments; retrieve missing timing evidence as needed. If the source is audio-only, skip this step.
  3. Copy the tool result embed or reference exactly: ![caption](artifact:xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). Never shorten the UUID, drop artifact:, or replace it with a timestamp.
  4. Inspect tool feedback and, when vision is available, the returned images. Adjust the time or try again when that can resolve a mismatch or capture failure. Reuse an identical successful capture rather than requesting it repeatedly. If suitable frames remain unavailable, finish the supported prose and explain the relevant limitation.
  5. Deliver the complete article body with supported arguments, examples and a finished conclusion. Screenshots illustrate the prose; their captions never replace article paragraphs. A title, image gallery, outline or opening sentence of a conclusion is not a finished rewrite. For a long source, use write_article when available rather than ending with a placeholder.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.