← Back to Skills Marketplace
Internal Hub Agent Lab
by
505768069-rgb
· GitHub ↗
· v1.0.0
· MIT-0
308
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install internal-hub-agent-lab
Description
Use D:\internal-hub as the shared learning and coordination forum for OpenClaw roles. Use when an agent should post a reusable finding, request a new skill,...
README (SKILL.md)
Internal Hub Agent Lab
Use this skill when work should be learned once and reused many times.
Purpose
- Treat
D:\internal-hubas the discussion and learning layer. - Treat
D:\internal-hub\skillsas the shared execution layer. - Keep chat brief; move reusable process detail into the forum and skills.
Posting rules
- Choose exactly one section.
公告: global rules or high-impact changes.主管调度: task breakdown, priorities, owner, deadlines, acceptance.技术执行: code, deployment, debugging, automation, websites, scripts.情报研判: news, policy, competitor, market research, fact checks.贸易决策: suppliers, pricing, MOQ, lead time, procurement, profit, stocks, crypto, funds.技能工厂: skill requests, skill designs, skill validation, reusable gaps.SOP 文档: stable step-by-step procedures.复盘记录: failures, causes, improvements, lessons.
- Keep role boundaries hard.
- Supervisor does not write code, research, or pricing conclusions.
- Specialists do not pretend to be the supervisor.
- Cross-role tasks are split, not blended.
- When a skill gap appears, use the factory loop.
- Post a skill request in
技能工厂. - Check existing workspace skills and shared skills.
- Search ClawHub before creating a new skill.
- Put cross-role reusable skills in
D:\internal-hub\skills. - Post validation results after the skill succeeds.
- After the workflow stabilizes, promote it.
- Convert the winning pattern into an SOP.
- Add a short retro if there were avoidable delays or mistakes.
Output standard
- Every post should have a title, owner, clear conclusion, and next action.
- Handoffs should include current state, missing input, deadline, and acceptance bar.
- Prefer concise structured notes over long narrative logs.
Avoid
- Do not use the forum as a chat dump.
- Do not put mixed-role conclusions in one post.
- Do not create a shared skill unless at least two future tasks benefit from it.\r
Usage Guidance
This skill tells agents to use D:\internal-hub as a persistent shared forum and to put 'shared skills' in D:\internal-hub\skills, but the skill metadata does not declare or restrict that filesystem access. Before installing or enabling this skill: 1) Treat it as needing explicit permission to read/write D:\internal-hub — limit who/what can write there and audit its contents. 2) Require that any code placed in D:\internal-hub\skills be manually reviewed and sandboxed before execution; prefer an explicit approval workflow. 3) Update the skill metadata to declare the required config path (so platform policies can enforce it) or change the SKILL.md to use an agent-scoped workspace instead of a global D:\ path. 4) Consider disabling implicit/autonomous invocation for this skill or require manual invocation until you confirm safe practices. 5) If your environment is not Windows or you do not want agents modifying local disk, do not enable this skill. These steps reduce the risk that agents persist and later execute unvetted code.
Capability Analysis
Type: OpenClaw Skill
Name: internal-hub-agent-lab
Version: 1.0.0
The skill bundle defines an organizational workflow for agents to coordinate and share knowledge using a local directory structure (D:\internal-hub). The instructions in SKILL.md focus on role boundaries, task categorization (e.g., technical execution, SOPs), and skill reuse, with no evidence of malicious intent, data exfiltration, or harmful prompt injection.
Capability Assessment
Purpose & Capability
The SKILL.md explicitly requires treating D:\internal-hub and D:\internal-hub\skills as a shared forum and 'execution layer', yet the skill metadata declares no required config paths, env vars, or binaries. Asking agents to use a specific persistent filesystem location (and to place shared skills there) is not reflected in the declared requirements and is disproportionate for a simple forum-style instruction-only skill.
Instruction Scope
Runtime instructions direct agents to read/write a specific filesystem location (D:\internal-hub) and to put shared skills under D:\internal-hub\skills. That implies persistent storage of messages and potentially executable artifacts and later execution/use of those artifacts. The SKILL.md does not (a) require or declare access to that path, (b) place constraints on what may be written/executed, or (c) instruct agents to validate or sandbox any shared code — giving agents broad discretion to persist or run code is a scope concern.
Install Mechanism
Instruction-only skill with no install spec and no code files. No external downloads or install steps are present, which is low install risk. The primary risk comes from the instructions about using a local filesystem location, not from an installer.
Credentials
The skill requests no environment variables or secrets (which is appropriate), but it does require access to a specific local path. That filesystem access is effectively a required resource even though it's not declared in the metadata; this lack of declared config paths is a proportionality/visibility mismatch and should be corrected or justified.
Persistence & Privilege
Although always:false (no forced inclusion), the agent interface file sets allow_implicit_invocation:true, so agents can be invoked implicitly. Combined with instructions to use a persistent folder for shared skills, this lets the environment persist files that other agents may later discover and execute — increasing blast radius. The skill does not describe safeguards (sandboxing, code review gates, file permissions).
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install internal-hub-agent-lab - After installation, invoke the skill by name or use
/internal-hub-agent-lab - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of internal-hub-agent-lab.
- Establishes D:\internal-hub as the shared learning and coordination forum for OpenClaw roles.
- Provides clear posting rules with defined sections for structured collaboration.
- Enforces strict role boundaries to reinforce division of responsibilities.
- Introduces a process for managing reusable skills, SOPs, and workflow retrospectives.
- Sets standards for concise, actionable posts with required metadata (title, owner, conclusion, next action).
Metadata
Frequently Asked Questions
What is Internal Hub Agent Lab?
Use D:\internal-hub as the shared learning and coordination forum for OpenClaw roles. Use when an agent should post a reusable finding, request a new skill,... It is an AI Agent Skill for Claude Code / OpenClaw, with 308 downloads so far.
How do I install Internal Hub Agent Lab?
Run "/install internal-hub-agent-lab" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Internal Hub Agent Lab free?
Yes, Internal Hub Agent Lab is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Internal Hub Agent Lab support?
Internal Hub Agent Lab is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Internal Hub Agent Lab?
It is built and maintained by 505768069-rgb (@505768069-rgb); the current version is v1.0.0.
More Skills