agentleFS
qwibitaiqwibitai/nanoclaw/.claude/skills/add-anydoc/SKILL.md

add-anydoc

Skill31k starsChanged 9 days agoMITView on GitHub

Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when agents need to read attached Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, or text-based PDF files without uploading them to a hosted parser.

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 4 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

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

    Read CONTRIBUTING.md, docs/skill-guidelines.md, and the supply-chain section of docs/SECURITY.md.

    line 12
  2. Distinctive:

    Run this check against the official npm registry before changing files:

    line 13
  3. Very specific:

    Stop on any failure. Do not install a PR commit, add a minimumReleaseAgeExclude, enable lifecycle scripts, or silently substitute another …

    line 35
  4. Very specific:

    Check whether container/skills/convert-documents-to-markdown/SKILL.md and src/anydoc-manifest.test.ts already exist.

    line 41
  5. Very specific:

    If data/v2.db exists, inspect per-group image pins before changing files.

    line 42
  6. Very specific:

    If the manifest has no AnyDoc entry, append this exact object to its JSON array.

    line 82
  7. Distinctive:

    Run validation before building the image:

    line 90
  8. Distinctive:

    If pnpm rejects the package as too new, stop.

    line 98
  9. Very specific:

    If timeout is absent, remove its wrapper from the installed container skill.

    line 129
  10. Very specific:

    Run only the command for the current platform.

    line 143
  11. Distinctive:

    Use one real channel attachment and verify the complete path:

    line 147

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Add AnyDoc

Install one pinned CLI and one focused container skill. Keep document conversion inside the agent container; do not change NanoClaw's attachment pipeline or add credentials, an MCP server, or a hosted parser.

Preflight

  1. Read CONTRIBUTING.md, docs/skill-guidelines.md, and the supply-chain section of docs/SECURITY.md.
  2. Run this check against the official npm registry before changing files:

    curl -fsSL "https://registry.npmjs.org/@firecrawl%2Fanydoc" | node -e '
      let body = "";
      process.stdin.setEncoding("utf8");
      process.stdin.on("data", (chunk) => (body += chunk));
      process.stdin.on("end", () => {
        const metadata = JSON.parse(body);
        const version = "0.1.6";
        const release = metadata.versions?.[version];
        const publishedAt = Date.parse(metadata.time?.[version] ?? "");
        const eligibleAt = publishedAt + 72 * 60 * 60 * 1000;
        if (!release) throw new Error(`${version} is missing from the registry`);
        if (release.deprecated) throw new Error(`${version} is deprecated: ${release.deprecated}`);
        if (!Number.isFinite(publishedAt)) throw new Error(`missing publish time for ${version}`);
        if (Date.now() < eligibleAt) throw new Error(`${version} is gated until ${new Date(eligibleAt).toISOString()}`);
        console.log(`${version} passed the 72-hour release gate`);
      });
    '

    Stop on any failure. Do not install a PR commit, add a minimumReleaseAgeExclude, enable lifecycle scripts, or silently substitute another version, unless the user explicitly approves it.

  3. Inspect container/cli-tools.json for @firecrawl/anydoc before changing files:
    • No entry: continue.
    • Exactly one entry at 0.1.6: leave it unchanged.
    • A duplicate or any other version: stop and report the conflict.
  4. Check whether container/skills/convert-documents-to-markdown/SKILL.md and src/anydoc-manifest.test.ts already exist. Reapplying this skill overwrites only those dedicated files.
  5. If data/v2.db exists, inspect per-group image pins before changing files. Standard derived images can be rebuilt from the updated shared image. Stop and report any other pin because its owner must decide how to rebuild it:

    if [ -f data/v2.db ]; then
      source setup/lib/install-slug.sh
      image_base="$(container_image_base)"
      foreign=0
      while IFS='|' read -r group_id image_tag package_count; do
        [ -z "$group_id" ] && continue
        if [ "$image_tag" != "${image_base}:${group_id}" ]; then
          echo "Foreign image pin: $group_id -> $image_tag" >&2
          foreign=1
        elif [ "$package_count" -eq 0 ]; then
          echo "Derived image cannot be rebuilt: $group_id has no configured packages" >&2
          foreign=1
        elif ! ncl groups get --id "$group_id" >/dev/null; then
          echo "Cannot reach NanoClaw through ncl for derived image: $group_id" >&2
          foreign=1
        fi
      done < <(pnpm exec tsx scripts/q.ts data/v2.db \
        "SELECT agent_group_id, image_tag, COALESCE(json_array_length(packages_apt), 0) + COALESCE(json_array_length(packages_npm), 0) FROM container_configs WHERE image_tag IS NOT NULL ORDER BY agent_group_id")
      [ "$foreign" -eq 0 ]
    fi

Install

Resolve this skill's bundled files from either Claude Code's skill variable or the project skill directory, then copy both files:

project_root="$(git rev-parse --show-toplevel)"
skill_dir="${CLAUDE_SKILL_DIR:-$project_root/.claude/skills/add-anydoc}"
test -f "$skill_dir/container-skills/convert-documents-to-markdown/SKILL.md"
test -f "$skill_dir/anydoc-manifest.test.ts"
mkdir -p container/skills/convert-documents-to-markdown
cp "$skill_dir/container-skills/convert-documents-to-markdown/SKILL.md" \
  container/skills/convert-documents-to-markdown/SKILL.md
cp "$skill_dir/anydoc-manifest.test.ts" src/anydoc-manifest.test.ts

If the manifest has no AnyDoc entry, append this exact object to its JSON array. Do not add onlyBuilt; the package and its prebuilt Linux bindings have no install lifecycle script.

{ "name": "@firecrawl/anydoc", "version": "0.1.6" }

Validate and build

Run validation before building the image:

pnpm exec vitest run src/anydoc-manifest.test.ts container/cli-tools.test.ts
pnpm run build
./container/build.sh

If pnpm rejects the package as too new, stop. Do not bypass the release-age policy.

Rebuild standard per-group images so groups with custom packages inherit the updated shared image:

if [ -f data/v2.db ]; then
  source setup/lib/install-slug.sh
  image_base="$(container_image_base)"
  while IFS='|' read -r group_id image_tag; do
    [ -z "$group_id" ] && continue
    if [ "$image_tag" != "${image_base}:${group_id}" ]; then
      echo "Foreign image pin appeared during install: $group_id -> $image_tag" >&2
      exit 1
    fi
    ncl groups restart --id "$group_id" --rebuild
  done < <(pnpm exec tsx scripts/q.ts data/v2.db \
    "SELECT agent_group_id, image_tag FROM container_configs WHERE image_tag IS NOT NULL ORDER BY agent_group_id")
fi

Resolve this install's image name and exercise the native binding, not only the help path:

source setup/lib/install-slug.sh
image="$(container_image_base):latest"
docker run --rm --entrypoint anydoc "$image" --version
printf 'name,count\nalpha,2\n' | \
  docker run --rm -i --entrypoint anydoc "$image" - --format csv | grep -q alpha
docker run --rm --entrypoint sh "$image" -c 'command -v timeout'

If timeout is absent, remove its wrapper from the installed container skill; do not add another dependency. Convert local DOCX, PPTX, and XLSX fixtures when available. Do not add private or large binary fixtures to the repository.

Restart

Restart this NanoClaw service only, so its running containers stop and default skills: "all" groups receive the new shared skill on their next spawn:

source setup/lib/install-slug.sh
# macOS
launchctl kickstart -k "gui/$(id -u)/$(launchd_label)"
# Linux
systemctl --user restart "$(systemd_unit)"

Run only the command for the current platform. If NanoClaw is not service-managed, stop this install's running agent containers by their nanoclaw-install=<install-slug> label instead of matching every nanoclaw-v2 container on the host.

Smoke test

Use one real channel attachment and verify the complete path:

  1. Confirm the message supplies an absolute local path such as /workspace/inbox/<message-id>/<file>, and use that exact path.
  2. Convert it to /workspace/agent/converted/ and summarize only the relevant Markdown sections.
  3. Confirm an image-only PDF fails clearly and is not uploaded anywhere.
  4. For agents open to unknown senders, recommend an operator-set CONTAINER_MEMORY_LIMIT; AnyDoc's parser caps decompression, but NanoClaw containers have no memory limit by default.

Report that office documents now convert locally. Call out that scanned PDFs need OCR, embedded visuals may be incomplete, and spreadsheet Markdown is not authoritative for calculations.

Download now (ZIP)

Trending

Quiet since July.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 15 mentionsMar 2026: 42 mentionsApr 2026: 7 mentionsMay 2026: 12 mentionsJun 2026: 2 mentionsJul 2026: 1 mentionAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the qwibitai/nanoclaw repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about qwibitai/nanoclaw

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

See all 79

Talked about on GitHub, YouTube, Bluesky and Hacker News (79 times).

On GitHub · 50

45 more on GitHub

On YouTube · 22

17 more on YouTube

On Bluesky · 6

1 more on Bluesky

On Hacker News · 1

Does it work?

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

Reviews can't be read right now.

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.