Private Domain Operator
v1.0.0Expert AI agent specializing in private domain operator. From The Agency (github.com/msitarzewski/agency-agents).
⭐ 0· 53·0 current·0 all-time
by@zhouqkt
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (Private Domain Operator) matches the content: operational guidance, SOPs, YAML/SQL/Python examples and strategy for WeCom private-domain operations. There are no unrelated requirements (no binaries, env vars, or installs) that are disproportionate to the stated purpose.
Instruction Scope
SKILL.md and associated docs are role/style/memory guidance and example configurations/SOPs. They do not instruct the agent to read local files, exfiltrate data, call external endpoints, or access credentials. The instructions are narrowly scoped to advisory and configuration examples.
Install Mechanism
No install spec and no code files—this is instruction-only. That is the lowest-risk install model and consistent with a documentation/assistant skill.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. This is proportional for a consultant/guide. Note: real integrations described in the docs (WeCom, SCRM, Mini Program) would require credentials if you later connect the agent to live systems, but the skill itself does not request them.
Persistence & Privilege
always is false and model invocation is allowed (the platform default). The skill does not request persistent system-level presence or attempt to modify other skills or system configs.
Assessment
This skill is a documentation-style/systems-advice assistant for WeCom private-domain operations and appears internally consistent and low-risk as distributed (instruction-only, no installs, no credentials requested). Before using it in a production agent: (1) do not provide any WeCom/SCRM API keys or service tokens to the agent unless you trust and have audited the integration code that will use them; (2) ensure any automation that sends messages complies with WeCom rules and local privacy laws (PIPL); (3) if a future version adds an install step or required env vars, inspect the install source and the exact variables requested before granting them; and (4) limit autonomous/outbound actions (message sending, friend-adding) via platform policy controls or human approval to avoid accidental mass messaging or policy violations.Like a lobster shell, security has layers — review code before you run it.
agencyvk974aq9a8b177m177z7p4kdp2n84phb3ai-agentsvk974aq9a8b177m177z7p4kdp2n84phb3latestvk974aq9a8b177m177z7p4kdp2n84phb3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔒 Clawdis