Openclaw Workflow Analyzer
v1.0.0分析用户的工作流程,判断哪些环节可以用 OpenClaw(个人 AI Agent)自动化实现。 将工作流拆解为子流程,按 ⭐1-10 星难度阶梯评估可行性,对第三方数据依赖主动确认可用性, 给出先易后难的落地建议和学习路径。 触发词:分析工作流程、workflow analysis、哪些可以自动化、OpenCla...
⭐ 0· 67·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (workflow analysis for OpenClaw automation) matches the SKILL.md content: it decomposes flows, assesses feasibility against OpenClaw capabilities, and explicitly says it will not perform automations. It requires the included references/openclaw-capabilities.md to evaluate feasibility, which is sensible for this purpose.
Instruction Scope
Runtime instructions are limited to asking the user for workflow details, decomposing steps, checking third-party data availability via user confirmation, rating difficulty, and producing a report. The SKILL.md does not instruct the agent to read system files, access environment variables, or transmit data to external endpoints. It explicitly requires asking users about APIs/credentials rather than assuming access.
Install Mechanism
No install spec and no code files beyond SKILL.md and a local reference file. Instruction-only skills write nothing to disk and do not pull external code, so install risk is minimal.
Credentials
The skill declares no required environment variables, credentials, or config paths. It instructs the agent to ask the user about third-party APIs and credentials only when needed for feasibility assessment, which is proportionate.
Persistence & Privilege
Flags show always: false and normal invocation settings. The skill does not request persistent system presence or attempt to modify other skills or system-wide settings.
Assessment
This skill appears coherent and low-risk because it is instruction-only and asks you to confirm external data access rather than obtaining credentials itself. Before installing or using it: (1) verify the GitHub homepage and author if you want provenance assurance; (2) do not paste sensitive credentials or secrets directly into chat—if you need to provide API keys for analysis, use the platform's secure secret storage or discuss only the existence/capabilities of the API without sharing tokens; (3) understand that the skill may recommend automations that require elevated access (APIs, browser automation, mobile control)—only grant those accesses after reviewing the proposed implementation and limiting scopes/expiration where possible; (4) if the skill suggests running scripts or connectors, prefer staged validation (test on non-production data); (5) if you need stronger guarantees (auditability, enterprise controls, encryption), remember the references file notes OpenClaw has limitations for high-compliance or multi-tenant scenarios. Overall: OK to install for workflow analysis, but follow standard secret-handling and access-minimization practices when acting on its recommendations.Like a lobster shell, security has layers — review code before you run it.
latestvk975et0j80b4vrmt4qh8s1d7vs83nzx2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
