Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Upload files to lmfiles.com and return public download links via API. Use when a user wants CLI-based file hosting, quick share links, bot-accessible file up...
Upload files to lmfiles.com and return public download links via API. Use when a user wants CLI-based file hosting, quick share links, bot-accessible file up...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use lmfiles.com as a lightweight file host for OpenClaw/LLM workflows.
Service docs: https://lmfiles.com/docs OpenAPI schema: https://lmfiles.com/openapi.json API host: https://lmfiles.com Primary credential: LMFILES_API_KEY (required for authenticated operations) Bootstrap credential: LMFILES_BOOTSTRAP_TOKEN (used only for first-time account registration) Security notes: Treat credentials as secrets and avoid logging/pasting them. Rotate bootstrap token if exposed. 401 Unauthorized usually means missing/invalid LMFILES_API_KEY.
Register an account once with a bootstrap token. Save returned api_key as LMFILES_API_KEY. Use LMFILES_API_KEY for all authenticated operations. Quick setup: export LMFILES_BOOTSTRAP_TOKEN="<bootstrap-token>" curl -sS -X POST https://lmfiles.com/api/v1/accounts/register \ -H "Content-Type: application/json" \ -d '{"username":"my-bot","bootstrap_token":"'"$LMFILES_BOOTSTRAP_TOKEN"'"}' # Copy api_key from response, then: export LMFILES_API_KEY="lmf_..." Common auth error: 401 Unauthorized = missing/invalid LMFILES_API_KEY.
LMFILES_API_KEY for authenticated file operations (primary credential). LMFILES_BOOTSTRAP_TOKEN only for account registration (bootstrap credential).
curl -sS -X POST https://lmfiles.com/api/v1/accounts/register \ -H "Content-Type: application/json" \ -d '{"username":"my-bot","bootstrap_token":"'"$LMFILES_BOOTSTRAP_TOKEN"'"}' Or use helper script: bash scripts/register.sh my-bot Save returned api_key as LMFILES_API_KEY.
curl -sS -X POST https://lmfiles.com/api/v1/files/upload \ -H "X-API-Key: $LMFILES_API_KEY" \ -F "file=@/absolute/path/to/file.ext" Expected response includes: file_id url (public download link)
curl -L "https://lmfiles.com/f/<file_id>" -o downloaded.file
curl -sS "https://lmfiles.com/api/v1/files/<file_id>"
curl -sS https://lmfiles.com/api/v1/accounts/me \ -H "X-API-Key: $LMFILES_API_KEY"
curl -sS https://lmfiles.com/api/v1/accounts/me/files \ -H "X-API-Key: $LMFILES_API_KEY" Or helper script: bash scripts/list.sh
curl -sS -X DELETE https://lmfiles.com/api/v1/files/<file_id> \ -H "X-API-Key: $LMFILES_API_KEY" Or helper script: bash scripts/delete.sh <file_id>
Max upload size: 100 MB. Executable file types are rejected (for example .php, .sh, .py, .exe). Files expire after 90 days of inactivity; downloads reset the expiry clock. Downloads are public for anyone with the URL.
Confirm file is safe to publish publicly. Avoid uploading secrets or credentials. If uncertain, ask user before upload.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.