agentleFS
fabioc-alohafabioc-aloha/Alex_ACT_ONE/skills/convert/SKILL.md

convert

Skill0 starsChanged 9 days agoMITView on GitHub

Convert a document between Markdown, HTML, Word, email, and plain text using the matching bundled converter. Use when the user asks to transform a supported document format.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    If the generic skill tool is unavailable for a converter, resolve the installed alex-act-one root and read the matching …

    line 11
  2. Very specific:

    Load format skill: Read the matching skill from skills/<format>/SKILL.md for format-specific rules and options.

    line 16
  3. Distinctive:

    Ask which file to convert.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “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

/convert

Convert a document to another format.

If the generic skill tool is unavailable for a converter, resolve the installed alex-act-one root and read the matching skills/<format>/SKILL.md directly. Do not declare the converter absent when its installed file exists.

Steps

  1. Detect formats: Identify the source file and target format from the user's request. If ambiguous, ask.
  2. Load format skill: Read the matching skill from skills/<format>/SKILL.md for format-specific rules and options.
  3. Run script: Execute the conversion script with the user's options:
    node skills/<format>/scripts/<format>.cjs <source> [output] [options]
  4. Validate: Confirm the output exists, is non-empty, and opens in the appropriate viewer. Use converter diagnostics for format-specific failures.
  5. Report: Show the output path, file size, and any diagnostics.

Format Detection

User saysSourceTargetScript
"convert to word" / "make a docx".md.docxskills/md-to-word/scripts/md-to-word.cjs
"convert to html" / "make a webpage".md.htmlskills/md-to-html/scripts/md-to-html.cjs
"convert to email" / "make an eml".md.emlskills/md-to-eml/scripts/md-to-eml.cjs
"convert to plain text".md.txtskills/md-to-txt/scripts/md-to-txt.cjs
"convert this word doc" / "docx to md".docx.mdskills/docx-to-md/scripts/docx-to-md.cjs
"convert this html" / "html to md".html.mdskills/html-to-md/scripts/html-to-md.cjs

If the user provides no file

Ask which file to convert. Do not guess.

Would Revise If

Revisit this prompt if the workflow ceases to produce its intended output, required verification is bypassed, or the slash-command is no longer discoverable in the prompt picker.

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.