agentleFS
CloudChefCloudChef/atlasclaw-providers/skills/text/SKILL.md

text

Skill17 starsChanged 6 months agoApache-2.0View on GitHub

Use this skill when the user wants to create, generate, save, export, download, convert, format, clean, or localize plain text, TXT, Markdown/MD, or HTML file deliverables. This skill produces text-family artifacts such as .txt, .text, .md, .markdown, or .html files and exposes the final file for download.

  • Reads credentials

5 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

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    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:

    When producing a user-facing .txt, .md, .markdown, or .html file:

    line 111
  2. Very specific:

    Write only the final content under the current work_dir, preferably exports/<descriptive-name>.<ext> unless the user requested a safe …

    line 113
  3. Distinctive:

    Use UTF-8 text. For HTML, produce a complete standalone document when the user asks for an HTML file.

    line 114
  4. Distinctive:

    Prefer writing a new output file instead of editing source files in place unless the user explicitly asks for an in-place edit.

    line 116
  5. Distinctive:

    Do not expose scripts, logs, caches, hidden files, intermediate files, or source documents as downloads.

    line 117
  6. Distinctive:

    Remove BOM if present: write a normalized copy instead of editing the source in place.

    line 137

“Common” is measured: kept by at least 6 in 10 of the 4 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

AtlasClaw Workspace Output

When producing a user-facing .txt, .md, .markdown, or .html file:

  1. Write only the final content under the current work_dir, preferably exports/<descriptive-name>.<ext> unless the user requested a safe relative filename.
  2. Use UTF-8 text. For HTML, produce a complete standalone document when the user asks for an HTML file.
  3. Expose the final file through the existing workspace download flow by passing its work_dir-relative path as download_paths.
  4. Prefer writing a new output file instead of editing source files in place unless the user explicitly asks for an in-place edit.
  5. Do not expose scripts, logs, caches, hidden files, intermediate files, or source documents as downloads.

AtlasClaw Runtime Commands

Prefer skill_read, skill_write, and skill_edit for simple file operations. If a transformation needs shell features such as pipes, redirects, globs, or compound commands, run it through bash -lc '<command>' with explicitly named work_dir-relative files, or use a python3 -c command that reads and writes explicit paths. Do not read or print .env, key, token, cookie, or password files unless the user explicitly requests it and the output is redacted.

Quick Reference

TaskLoad
Text cleanup, extraction, Markdown, or HTML shapingdata.md
Translation/localization for text outputlocalization.md

Universal Text Rules

Encoding

  • Always verify encoding first: file -bi document.txt
  • Normalize line endings: tr -d '\r'
  • Remove BOM if present: write a normalized copy instead of editing the source in place.

Whitespace

  • Collapse multiple spaces: sed 's/[[:space:]]\+/ /g'
  • Trim leading/trailing: sed 's/^[[:space:]]*//;s/[[:space:]]*$//'

Common Traps

  • Smart quotes (\u201c, \u201d, \u2018, \u2019) break parsers -> normalize to ASCII quotes.
  • Em/en dashes (\u2013, \u2014) break ASCII-only output -> normalize to -.
  • Zero-width chars invisible but break comparisons → strip them
  • String length ≠ byte length in UTF-8 ("café" = 4 chars, 5 bytes)

Format Detection

# Detect encoding
file -I document.txt

# Detect line endings
cat -A document.txt | head -1
# ^M at end = Windows (CRLF)
# No ^M = Unix (LF)

# Detect likely HTML
grep -qiE '<html|<!doctype html' document.html

Quick Transformations

TaskCommand
Lowercasetr '[:upper:]' '[:lower:]'
Remove punctuationtr -d '[:punct:]'
Count wordswc -w
Count unique linessort -u | wc -l
Find duplicatessort | uniq -d
Extract emailsgrep -oE '[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\.[a-zA-Z]{2,}'
Extract URLs`grep -oE 'https?://[^[:space:]<>"{}\^\[\]]+'

Before Processing Checklist

  • Encoding verified (UTF-8?)
  • Line endings normalized
  • Target format/style defined (TXT, Markdown, or HTML)
  • Edge cases considered (empty, Unicode, special chars)

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.