← Back to Skills Marketplace
openclaw-threadsctl
by
Vladyslav Dobrodii
· GitHub ↗
· v1.0.2
· MIT-0
117
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install openclaw-threadsctl
Description
Manage Threads accounts, OAuth connect URLs, drafts, and publishing through the local `threadsctl` CLI. Use when the user wants to post to Threads, create or...
Usage Guidance
Before installing, confirm with the skill author or registry that THREADS_SERVICE_URL and THREADS_SERVICE_API_KEY are required and why; ask them to add those env/config requirements to the metadata. Do not grant the agent broad access to a production server root path (/root/.openclaw/media) or the /opt/threads-service-ts directory unless you control that environment. If you must use this skill, run it in a controlled/test environment, inspect the threadsctl binary and its configuration, and require explicit user confirmation for any publish action (avoid autonomous publishing). Consider limiting agent privileges or disabling autonomous invocation for this skill until the metadata and safeguards are clarified.
Capability Analysis
Type: OpenClaw Skill
Name: openclaw-threadsctl
Version: 1.0.2
The skill bundle provides instructions and examples for an AI agent to manage Threads accounts and publishing via a local CLI tool named `threadsctl`. It includes standard workflows for OAuth authentication, draft management, and media publishing, with safety rules such as requiring explicit user confirmation before posting. No evidence of malicious intent, data exfiltration, or unauthorized command execution was found in SKILL.md or examples.md.
Capability Tags
Capability Assessment
Purpose & Capability
The skill's name and description (threadsctl integration) match the instructions: it legitimately needs to run threadsctl and work with Threads accounts. However, the SKILL.md requires the THREADS_SERVICE_URL and THREADS_SERVICE_API_KEY and a specific runtime directory (/opt/threads-service-ts/threads-service) and local media path (/root/.openclaw/media), yet the registry metadata lists no required env vars or config paths. Those omissions are inconsistent and unexplained.
Instruction Scope
Instructions direct the agent to run CLI commands from a specific server directory and to use local files under /root/.openclaw/media, and to produce OAuth connect URLs for users. While these actions align with posting/connecting workflows, they expand the agent's scope into server-local files and credentials. The SKILL.md does not detail safeguards for handling secrets or limiting file access, creating scope creep risk.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, which is lower-risk from an installation perspective (nothing is downloaded or written to disk by the skill package itself).
Credentials
The runtime instructions explicitly require THREADS_SERVICE_URL and THREADS_SERVICE_API_KEY (sensitive credentials) and expect OpenClaw to save local media under /root/.openclaw/media, but the skill declares no required environment variables or primary credential. Sensitive requirements should be declared in the registry and justified; the current omission is disproportionate and opaque.
Persistence & Privilege
The skill does not request always:true and does not claim persistent system changes. Model invocation remains allowed (default), which is normal; however, autonomous execution combined with the undeclared credentials would increase risk if allowed without user confirmation.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install openclaw-threadsctl - After installation, invoke the skill by name or use
/openclaw-threadsctl - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
- Added requirements and best practices for running `threadsctl` commands from `/opt/threads-service-ts/threads-service` directory.
- Clarified when to use `--file` (for local image files under `/root/.openclaw/media/...`) versus `--media-url` (for already-hosted images).
- Updated command and workflow examples to include `cd /opt/threads-service-ts/threads-service` for context.
- Explicitly stated not to pass local filesystem paths to `--media-url`.
- Improved clarity around image publishing and directory convention for image assets.
v1.0.1
- Added prerequisite and environment requirements for using the skill (CLI setup, API keys, text/image model configuration).
- Clarified model-agnostic use and optional image generation (should be handled separately from posting).
- Added new workflow for handling image generation before publishing image posts.
- Explicitly stated not to assume an image generation provider unless actually configured.
- Included new rules regarding image publishing and media URLs.
- General documentation improvements and clarifications for broader compatibility.
v1.0.0
Initial release of openclaw-threadsctl.
- Provides a safe, user-friendly interface for managing Threads accounts and publishing via the local threadsctl CLI.
- Supports workflows for direct publishing, drafts, account management, and OAuth connection.
- Enforces usage of account labels, clear publishing intent, and descriptive error reporting.
- Offers concise result summaries to keep feedback readable and actionable.
- Includes built-in examples and command templates for common tasks.
Metadata
Frequently Asked Questions
What is openclaw-threadsctl?
Manage Threads accounts, OAuth connect URLs, drafts, and publishing through the local `threadsctl` CLI. Use when the user wants to post to Threads, create or... It is an AI Agent Skill for Claude Code / OpenClaw, with 117 downloads so far.
How do I install openclaw-threadsctl?
Run "/install openclaw-threadsctl" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is openclaw-threadsctl free?
Yes, openclaw-threadsctl is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does openclaw-threadsctl support?
openclaw-threadsctl is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created openclaw-threadsctl?
It is built and maintained by Vladyslav Dobrodii (@dladislav201); the current version is v1.0.2.
More Skills