MooTeam CRM

v1.0.0

MooTeam (moo.team) API v1 for OpenClaw: projects, teams, tasks, drafts, comments, workflows, statuses, labels, timer and time logs, activity logs. Requires M...

1· 76·0 current·0 all-time
byantokhin-seo@antokhin-digital
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (MooTeam CRM API) match the actual code and CLI commands. Required env vars (MOOTEAM_API_TOKEN, MOOTEAM_COMPANY_ALIAS) and python3 are appropriate and expected for this API integration.
Instruction Scope
SKILL.md instructs the agent to run the included Python CLI and to set the two environment variables; the runtime instructions and the code only interact with the MooTeam API and local CLI invocation. There are no instructions to read unrelated files or to send data to third-party endpoints.
Install Mechanism
Registry has no formal install spec, but SKILL.md documents manual installation steps (clawhub publish/install and pip install -r requirements.txt). Installation uses standard pip dependencies (requests, python-dotenv, rich). This is not high-risk, but it relies on the user running pip in a workspace — review dependencies and run in a virtual environment.
Credentials
Only two environment variables are required (API token and company alias) and they directly map to HTTP Authorization and a custom header. No unrelated secrets, config paths, or extraneous credentials are requested.
Persistence & Privilege
Skill is not force-included (always: false) and uses normal agent invocation. It does not request persistent system-wide privileges or modify other skills' configs. It requires the environment variables be available to the agent process (normal for API skills).
Assessment
This skill appears to do exactly what it says: a CLI wrapper around the MooTeam API. Before installing: (1) verify the domain (api.moo.team) matches your expected MooTeam service, (2) create a least-privilege API token for the agent rather than using a personal full-access key, (3) run pip install in an isolated virtualenv and review requirements.txt, (4) ensure MOOTEAM_API_TOKEN is stored and injected securely (gateway secrets, not plaintext in shared files), and (5) test the skill in a non-production workspace first. If you have doubts, inspect the included Python files (MooTeamClient.py and main.py) yourself — they are short and straightforward — to confirm there are no unexpected network endpoints or logging of secrets.

Like a lobster shell, security has layers — review code before you run it.

latestvk978xtdjw60vka8pa1zevcsfzd83c2ck

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🐂 Clawdis
Binspython3
EnvMOOTEAM_API_TOKEN, MOOTEAM_COMPANY_ALIAS
Primary envMOOTEAM_API_TOKEN

Comments