Ceo Assistant
v1.0.0A master AI assistant for CEOs and executives. Helps with end-to-end planning, executing, and completing tasks and projects, including goal clarification, st...
⭐ 0· 62·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
Name and description (executive planning, execution, review) align with the SKILL.md instructions (goal clarification, plan→execute→review, proactive assistance). There are no unrelated requirements (no env vars, no binaries).
Instruction Scope
Instructions remain within expected assistant behavior (decompose goals, propose plans, execute or guide execution). The doc explicitly allows taking actions autonomously when appropriate — this is consistent with a proactive assistant but broad in practice and depends on what other skills/integrations the agent has access to.
Install Mechanism
No install spec and no code files (instruction-only). This minimizes on-disk risk; nothing is downloaded or executed from external sources by the skill itself.
Credentials
Skill declares no required environment variables, credentials, or config paths. It does not request access to unrelated services or secrets.
Persistence & Privilege
The skill is not always-enabled and does not request persistent system-wide changes. However, its guidance to 'take action autonomously when appropriate' increases the effective privilege if the agent has other action-capable integrations (email, calendar, cloud APIs). That risk stems from platform-level integrations, not this skill's content.
Assessment
This skill is instruction-only and coherent with its stated purpose, but be mindful of what the agent can do in your environment: 1) Review and limit other integrations/skills (email, calendar, ticketing, cloud, CI/CD) before giving this assistant broad autonomy. 2) If you want to prevent any automated changes, disable autonomous invocation for this skill or require manual confirmation for actions that affect external systems. 3) Test with low-risk tasks first (planning, checklists) to observe behavior. 4) Check agent logs/audit trails if available and avoid sharing sensitive credentials or private data unless strictly necessary. 5) If you plan to enable long-term memory for preferences, explicitly control what is stored and verify retention policies.Like a lobster shell, security has layers — review code before you run it.
latestvk97bsrvzpsjd60hzjq9ykhtx1h84ek4g
License
MIT-0
Free to use, modify, and redistribute. No attribution required.