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.
When & Why to Use This Skill
The site-tools skill is a comprehensive automation framework designed for Claude agents to manage and execute a public script toolbox. By utilizing a specialized tool-runner, it enables the safe listing, downloading, and execution of repository-hosted scripts. This skill is optimized for creating reproducible workflows, handling environment-specific configurations, and integrating seamlessly with CI/CD pipelines like GitHub Actions for tasks such as data classification and manifest management.
Use Cases
- Automated Content Classification: Efficiently categorize feed entries or data files by executing specialized classification scripts through the tool-runner.
- CI/CD Pipeline Integration: Automate repository maintenance and data updates by incorporating toolbox scripts into GitHub Actions workflows.
- Secure Script Orchestration: Execute local or remote automation tools within a controlled 'droid exec' context to ensure security and environment consistency.
- Lightweight Data Processing: Run on-demand scripts for exporting statistics or processing repository artifacts without the need for a full application server infrastructure.
| name | site-tools |
|---|---|
| description | 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. |
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
- List tools
node docs/tools/tool-runner.js --list - Run a tool locally (prefers local script, falls back to public copy):
Example (dry run):node docs/tools/tool-runner.js <tool-name> --flag valueFACTORY_API_KEY=*** \ node docs/tools/tool-runner.js classify-feed --input docs/data/feed.json --dry-run - Environment: export
FACTORY_API_KEY(Factory CLI auth), optionalMODEL_ID=glm-4.6,MODEL_REASONING=low,CLASSIFIER_MAX_BATCH=10. LegacyGLM_*vars are still read but will be removed once all workflows migrate. - Autonomy & safety: prefer
droid execread-only flows; only enable higher autonomy or repo mutations if the tool explicitly states so. Inspect scripts underdocs/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-runto 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
- Skills format: https://docs.factory.ai/cli/configuration/skills
- droid exec usage: https://docs.factory.ai/cli/droid-exec/overview.md