Temp Publish
v0.0.1Skill Cortex is the system's capability cortex. When lacking ability, it autonomously acquires Skills from ClawHub or GitHub, then releases them after use. E...
⭐ 0· 316·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill requires the clawhub binary and its instructions revolve around searching, installing, running, and uninstalling Skills from ClawHub/GitHub and maintaining a local cortex.json — all of which are coherent with a 'Skill Cortex' that dynamically acquires and caches Skills.
Instruction Scope
SKILL.md explicitly reads and writes a persistent file (~/.openclaw/skill-cortex/cortex.json) and instructs running 'clawhub search/install/uninstall' and occasional 'which <dependency>' checks — these are expected. However, there are contradictory instructions around candidate switching (Phase 3.1 says auto-switch on failure; a later line says switching requires user consent) and reflex behavior: reflex mode can skip the execution-plan confirmation (though it still shows an install notification). Those contradictions widen the agent's discretion and could lead to unexpected autonomous installs/executions if not strictly enforced.
Install Mechanism
This is instruction-only (no install spec), so nothing is written by this skill itself. It relies on the external 'clawhub' CLI to fetch and install other Skills; that dependency is appropriate for the stated functionality but means the actual code fetched and executed comes from third-party sources (ClawHub/GitHub) and is out of this skill's control.
Credentials
No environment variables or unrelated credentials are requested. The design intentionally records only variable NAMES (e.g., TODOIST_API_KEY) and not values in prefrontal 'env_ready' lessons, and the entity-filtering rules aim to avoid storing concrete personal identifiers — this aligns with the cortex's stated purpose.
Persistence & Privilege
The skill persists a local cortex.json and updates it after each invocation (weights, histories, lessons). That is within scope, but reflex mode (which grants faster, lower-friction invocation) can skip the execution-plan confirmation step; combined with autonomous invocation being allowed by default, this increases the blast radius if reflex promotion or the cortex file is manipulated. Also note the inconsistent language about auto-switching vs. requiring consent for candidate switching — this ambiguity affects how much autonomy the skill will exercise.
What to consider before installing
This skill appears to implement exactly what it claims (a temporary Skill fetch-and-run 'cortex'), but it gives the agent power to search/install third-party Skills via your clawhub CLI and to persist a local cortex.json. Before installing: 1) Ensure you trust the ClawHub/GitHub sources your agent will pull from and that clawhub is the official client. 2) Ask the author (or inspect published SKILL.md) to clarify the contradictions around auto-switching candidates and what reflex mode actually skips — you should be comfortable that installs and execution plans will be shown and require explicit consent. 3) Backup ~/.openclaw/skill-cortex/cortex.json and review its entity-filtering behavior if you have privacy concerns. 4) Consider limiting use to manual invocation until you verify reflex promotion behavior and candidate-switching semantics.Like a lobster shell, security has layers — review code before you run it.
latestvk9796n0sy3mh3ejpt9mwsgr3dh81z2nj
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binsclawhub