smithery/factory-ben

site-tools

Use the public toolbox scripts published from docs/tools via tool-runner.js. Covers listing tools, executing them safely with droid exec context, and required environment variables.

Installation

$ npx skills add smithery/factory-ben --skill site-tools

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,229 B
  • docs SUMMARY.md 199 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Site Toolbox Skill

Capability

Operate the public toolbox that ships with this repo. Each tool lives under docs/tools/<tool>/script.js and is mirrored to GitHub Pages (default base URL https://factory-ben.github.io/feed-aggregator). Use tool-runner.js to list, download (if needed), and execute tools so every automation step stays lightweight and reproducible.

How to use

  1. List tools

``bash node docs/tools/tool-runner.js --list ``

  1. Run a tool locally (prefers local script, falls back to public copy):

``bash node docs/tools/tool-runner.js <tool-name> --flag value ` Example (dry run): `bash FACTORYAPIKEY=*** \ node docs/tools/tool-runner.js classify-feed --input docs/data/feed.json --dry-run ``

  1. Environment: export FACTORYAPIKEY (Factory CLI auth), optional MODELID=glm-4.6, MODELREASONING=low, CLASSIFIERMAXBATCH=10. Legacy GLM_* vars are still read but will be removed once all workflows migrate.
  2. Autonomy & safety: prefer droid exec read-only flows; only enable higher autonomy or repo mutations if the tool explicitly states so. Inspect scripts under docs/tools/ before running remote copies.

Verification

  • After running toolbox commands that mutate repo files, run npm run build:tools (keeps manifest fresh) and any relevant validation commands noted by the tool. For the classifier, rerun with --dry-run to confirm GLM responses before writing.
  • All artifacts land in docs/data/ unless overridden. Commit outputs only after reviewing diffs.

When to reach for this skill

  • Need to classify feed entries, export stats, or run future automation hosted as simple scripts without inflating the app server.
  • Want a reproducible workflow that GitHub Actions can mirror (install Factory CLI, call tool-runner, push results).

References