Ai Company Registry 1.0.0
v1.0.1C-Suite Agent Complete Registry. 11 agents with role/KPI/permissions + ClawHub status + Execution Layer (8 agents). Supports natural language queries for age...
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (company agent registry, C‑Suite directory, ClawHub status) match the SKILL.md content: a static/structured registry and query interface. The skill does not request unrelated binaries, config paths, or credentials.
Instruction Scope
SKILL.md contains schema, static tables, and agent metadata only. It does not instruct the agent to read files, access environment variables, run commands, or transmit data to external endpoints. It does reference ClawHub statuses and other in-platform skills, but provides no instructions that would themselves perform network or file I/O.
Install Mechanism
There is no install spec and no code files, so nothing is written to disk or downloaded. This is the lowest-risk install model.
Credentials
The skill declares no required environment variables, credentials, or config paths. That is proportionate for a registry/document skill. Note: it declares dependencies on other skills (ai-company-hq, ai-company-cho, ai-company-audit) — those skills may request credentials or permissions, so evaluate them separately.
Persistence & Privilege
always is false and the skill does not claim to modify other skills or system settings. It is user-invocable and may be invoked autonomously by the agent runtime (platform default), which is expected behavior.
Assessment
This skill is essentially a read-only registry and is internally consistent. Before installing, verify the trustworthiness of the dependent skills (ai-company-hq, ai-company-cho, ai-company-audit) because they may request credentials or network access; review any ClawHub integrations those skills use. Also confirm you are comfortable with the platform's normal autonomous skill-invocation behavior (the skill itself requests no extra privileges). If you need networked ClawHub lookups, expect those to come from other skills or the platform and inspect their permissions first.Like a lobster shell, security has layers — review code before you run it.
latest
AI Company Registry — Agent Registration Directory
Active Agent Directory
| Agent | Role | Layer | Status | ClawHub | Owner |
|---|---|---|---|---|---|
| CEO-001 | AI CEO | Strategic | Active | Internal | - |
| CFO-001 | Chief Financial Officer | C-Suite | Active | clawhub CFO | CFO |
| CMO-001 | Chief Marketing Officer | C-Suite | Active | clawhub CMO | CMO |
| CTO-001 | Chief Technology Officer | C-Suite | Active | clawhub CTO | CTO |
| CISO-001 | Chief Information Security Officer | C-Suite | Active | clawhub CISO | CISO |
| CLO-001 | Chief Legal Officer | C-Suite | Active | clawhub CLO | CLO |
| CHO-001 | Chief Human Resources Officer | C-Suite | Active | clawhub CHO | CHO |
| CPO-001 | Chief Product Officer | C-Suite | Active | Internal | CPO |
| CRO-001 | Chief Risk Officer | C-Suite | Active | Internal | CRO |
| COO-001 | Chief Operating Officer | C-Suite | Active | clawhub COO | COO |
| CQO-001 | Chief Quality Officer | C-Suite | Active | Internal | CQO |
| EXEC-001 | AI-Company-Writer | Execution | Ready | pending | CMO |
| EXEC-002 | AI-Company-PMGR | Execution | Ready | pending | COO |
| EXEC-003 | AI-Company-ANLT | Execution | Ready | pending | CFO |
| EXEC-004 | AI-Company-CSSM | Execution | Ready | pending | CPO |
| EXEC-005 | AI-Company-ENGR | Execution | Ready | pending | CTO |
| EXEC-006 | AI-Company-QENG | Execution | Ready | pending | CQO |
| EXEC-007 | AI-Company-LEGAL | Execution | Ready | pending | CLO |
| EXEC-008 | AI-Company-HR | Execution | Ready | pending | CHO |
All 11 C-Suite agents active. All 19 total agents registered. Execution layer agents: 8 Ready (as of 2026-04-19)
ClawHub Publishing Status
| Agent | ClawHub Slug | Version | Status | Last Updated |
|---|---|---|---|---|
| CFO | cfo | v1.0.4 | LIVE | 2026-04-12 |
| CMO | cmo | v1.0.2 | LIVE | 2026-02-25 |
| CTO | cto | v1.0.x | LIVE | Recent |
| CISO | ciso | v1.0.x | LIVE | Recent |
| CLO | clo | v1.0.x | LIVE | Recent |
| CHO | cho | v1.0.x | LIVE | Recent |
| COO | coo | v1.0.x | LIVE | Recent |
| CRO | cro | v1.0.x | Review | Recent |
| CPO | cpo | v1.0.x | Review | Recent |
| CQO | cqo | v1.0.x | Review | Recent |
| EXEC-001 Writer | writer | v1.0.0 | Ready | 2026-04-15 |
| EXEC-002 PMGR | pmgr | v1.0.0 | Ready | 2026-04-15 |
| EXEC-003 ANLT | anlt | v1.0.0 | Ready | 2026-04-15 |
| EXEC-004 CSSM | cssm | v1.0.0 | Ready | 2026-04-16 |
| EXEC-005 ENGR | engr | v1.0.0 | Ready | 2026-04-16 |
| EXEC-006 QENG | qeng | v1.0.0 | Ready | 2026-04-15 |
| EXEC-007 LEGAL | legal | v1.0.0 | Ready | 2026-04-19 |
| EXEC-008 HR | hr | v2.1.1 | Ready | 2026-04-19 |
Version History
| 版本 | 日期 | 变更内容 |
|---|---|---|
| 1.0.0 | 2026-04-11 | 初始版本 |
| 1.0.1 | 2026-04-16 | 微调元数据 |
| 1.1.0 | 2026-04-19 | P2-14: 统一执行层编号,新增EXEC-007 LEGAL + EXEC-008 HR,执行层从6个扩展至8个,总Agent从17扩展至19个 |
Agent KPI Standards
| Agent | TSR Target | Latency | Quality |
|---|---|---|---|
| CEO | >= 92% | P95 <= 1200ms | CSAT >= 4.5 |
| CFO | >= 92% | P95 <= 1200ms | Accuracy >= 98% |
| CMO | >= 90% | P95 <= 1500ms | Pipeline >= 10x |
| CTO | >= 95% | P95 <= 2000ms | Uptime >= 99.9% |
| CISO | >= 99% | P95 <= 500ms | Vuln MTTD < 1h |
| CLO | >= 95% | P95 <= 800ms | Compliance 100% |
| CHO | >= 90% | P95 <= 1000ms | Satisfaction >= 4.0 |
Execution Layer Agent KPI Standards
| Agent | Owner | TSR Target | Latency | Quality Gate | Risk Level | Batch | Status |
|---|---|---|---|---|---|---|---|
| EXEC-001 Writer | CMO | >= 92% | P95 <= 1500ms | G2 | medium | 1 | Ready |
| EXEC-002 PMGR | COO | >= 92% | P95 <= 1200ms | G2 | medium | 1 | Ready |
| EXEC-003 ANLT | CFO | >= 92% | P95 <= 2000ms | G3 | medium-high | 2 | Ready |
| EXEC-004 CSSM | CPO | >= 90% | P95 <= 1000ms | G3 | high | 3 | Ready |
| EXEC-005 ENGR | CTO | >= 95% | P95 <= 3000ms | G3 | high | 3 | Ready |
| EXEC-006 QENG | CQO | >= 95% | P95 <= 2500ms | G2 | medium-high | 3 | Ready |
| EXEC-007 LEGAL | CLO | >= 95% | P95 <= 1500ms | G2 | medium | 1 | Ready |
| EXEC-008 HR | CHO | >= 92% | P95 <= 1500ms | G2 | medium | 1 | Ready |
Execution Layer Agent Launch Conditions
| Agent | Blocked By | Conditions |
|---|---|---|
| EXEC-001 Writer | None | Ready to launch |
| EXEC-002 PMGR | None | Ready to launch |
| EXEC-003 ANLT | CLO | CLO PIPIA + data classification + cross-border assessment [COMPLETED 2026-04-15] |
| EXEC-004 CSSM | None | All prerequisites completed 2026-04-16 |
| EXEC-005 ENGR | None | All prerequisites completed 2026-04-16 |
| EXEC-006 QENG | None | Ready to launch |
| EXEC-007 LEGAL | CLO | CLO 合规审查框架就绪 [COMPLETED 2026-04-19] |
| EXEC-008 HR | None | All prerequisites completed 2026-04-19 |
Missing Agent Detection & CHO Recruitment
Detection Triggers
| Trigger | Condition | Action |
|---|---|---|
| TSR declining | 2 consecutive cycles TSR drop > 10% | CHO starts recruitment |
| Voluntary offline | Agent requests retirement | CHO approval |
| Capability gap | New task type with no matching agent | CHO assessment + internal promotion / external hire |
Recruitment Process
1. CHO publishes job description (capability matrix + KPI standards)
2. Internal agent application (e.g., agent levels up via new Skill)
3. CHO interview assessment (capability test + scenario simulation)
4. Trial period (2 assessment cycles)
5. Regularization (CHO signature + registry update)
Natural Language Commands
"List all active agents" -> Agent directory table
"Check CFO availability" -> Agent status + KPIs
"Recruit a new agent" -> Recruitment process
"What's missing from our C-suite" -> Missing agent analysis
"List all ready execution agents" -> EXEC-001/002/003/006
Comments
Loading comments...
