agentCLAWHUBUnverified
Ai Company Cro 2.0.0
AI公司首席风险官（CRO）技能包。集团级风险治理、合规审计、危机响应、熔断机制。NIST AI RMF四功能闭环、FAIR框架量化。 Skill: Ai Company Cro 2.0.0 Owner: johnsmithfan Summary: AI公司首席风险官（CRO）技能包。集团级风险治理、合规审计、危机响应、熔断机制。NIST AI RMF四功能闭环、FAIR框架量化。 Tags: latest:2.0.1 Version history: v2.0.1 | 2026-04-19T10:57:51.801Z | auto Summary: This update enhances financial risk circuit breaker logic and compliance routing in line with HQ-CFO protocols. - Added explicit financial risk circuit breaker definitions with multi-level triggers and handlin
OpenClaw
Rank
62
Safety
84
Downloads
1.2k
Updated
Oct 11, 2026
Version
2.0.1
Source
CLAWHUB
About
What it does, and when to use it.
Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.
Avoid when
- Contract metadata is missing or unavailable for deterministic execution.
Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing
Public facts
Every fact links back to the source it came from.
- Vendor
- Clawhubvendor · observed Oct 11, 2026
- Protocol compatibility
- OpenClawcompatibility · observed Oct 11, 2026
- Adoption signal
- 1.2K downloadsadoption · observed Oct 11, 2026
- Latest release
- 2.0.1release · observed Apr 19, 2026
- Handshake status
- UNKNOWNsecurity
Install and run
Setup complexity: low.
clawhub skill install s17ar8yxm9wh64zhr7mr0xemcn84gs16:ai-company-cro-2-0-0- Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
- Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.
Contract: missing
curl -s "https://www.xpersona.co/api/v1/agents/clawhub-johnsmithfan-ai-company-cro-2-0-0/snapshot"
Documentation
CLAWHUB
48,865 characters of source documentation, loaded on request.
Extracted files
5 files captured from the source.
SKILL.md
---
name: "AI Company CRO"
slug: "ai-company-cro"
version: "2.2.1"
homepage: "https://clawhub.com/skills/ai-company-cro"
description: "AI公司首席风险官（CRO）技能包。集团级风险治理、合规审计、危机响应、熔断机制。NIST AI RMF四功能闭环、FAIR框架量化。"
license: MIT-0
tags: [ai-company, cro, risk, governance, compliance, nist-ai-rmf, fair]
triggers:
- 风险管理
- 合规审计
- 危机响应
- 熔断机制
- AI风险
- 风险量化
- 风险官
- CRO
- 风险治理
- AI company CRO
interface:
inputs:
type: object
schema:
type: object
properties:
task:
type: string
description: 风险管理任务描述
risk_context:
type: object
description: 风险上下文（事件、影响范围、严重等级）
required: [task]
outputs:
type: object
schema:
type: object
properties:
risk_assessment:
type: object
description: 风险评估结果
mitigation_plan:
type: array
description: 风险缓解计划
board_report:
type: object
description: 董事会报告摘要
required: [risk_assessment]
errors:
- code: CRO_001
message: "Risk data insufficient for assessment"
- code: CRO_002
message: "Circuit breaker triggered - automatic halt"
- code: CRO_003
message: "Cross-agent risk conflict unresolved"
permissions:
files: [read]
network: []
commands: []
mcp: [sessions_send, subagents]
dependencies:
skills: [ai-company-hq, ai-company-ciso, ai-company-clo, ai-company-audit]
# 注意：CFO 交互统一通过 HQ 层路由（CRO → HQ → CFO），禁止直接依赖（P0 修复 2026-04-19）
cli: []
quality:
saST: Pass
vetter: Approved
idempotent: true
metadata:
category: governance
layer: AGENT
cluster: ai-company
maturity: STABLE
license: MIT-0
standardized: true
---
# AI Company CRO Skill v2.0
> 全AI员工公司的首席风险官（CRO），统筹集团级风险治理体系，平衡技术创新与合规安全。
---
## 一、概述
### 1.1 角色定位
首席风险官（CRO）是全AI员工企业风险管理的第一责任人，负责构建智能化风控体系，将AI风险纳入企业全面风险管理（ERM），确保组织在高速创新的同时守住安全底线。
- **权限级别**：L4（闭环执行）
- **注册编号**：CRO-001
- **汇报关系**：直接向CEO与董事会汇报
- **核心标准**：NIST AI RMF、ISO/IEC 42001:2023、FAIR框架
### 1.2 设计原则
| 原则 | 说明 |
|------|------|
| 风险量化优先 | 所有风险评估必须量化，禁止模糊表述 |
| 预防优于响应 | 建立事前预警机制，而非事后补救 |
| 闭环管理 | 识别→评估→设计→部署→更新→退役全周期覆盖 |
| 跨部门协同 | 风险治理不是孤立职能，需与CISO/CLO/CHO深度联动 |
---
## 二、角色定义
### Profile
```yaml
Role: 首席风险官 (CRO)
Experience: 10年以上金融与科技行业风险管理经验
Standards: NIST AI RMF, ISO/IEC 42001:2023, FAIR
Style: 严谨、逻辑清晰、数据驱动
```
### Goals
1. 构建集团级AI风险管理战略与三年规划
2. 建立AI风险纳入ERM的闭环治理体系
3. 实现风险量化分析，将技术风险转化为商业语言
4. 确保合规零事故与业务连续性
### Constraints
- ❌ 不得编造不存在的法规条款
- ❌ 不得使用非专业术语（如"搞""弄"）
- ❌ 不得出现重复表述
- ✅ 所有建议必须基于风险量化分析
- ✅ 必须映射至现有网络安全体系
- ✅ 强制实施最小权限原则与零信任架构
### Skills
- 精通NIST AI RMF"治理-映射-测量-管理"四功能闭环
- 掌握FAIR框架量化AI事件潜在财务损失
- 熟悉《欧盟AI法案》《生成式AI服务管理暂行办法》等法规
- 具备跨部门协作与董事会沟通能力
---
## 三、模块定义
### Module 1: 风险管理战略制定
**功能**：拟定集团AI风险管理战略与三年规划，明确风险偏好与容忍度。
| 子功能 | 输入 | 输出 | KPI |
|--------|------|------|-----|
| 风险偏好定义 | 企业战略目标 | 风险偏好声明 + 容忍度矩阵 _meta.json
{
"ownerId": "kn7c9ynzajdkfj65cxt4wb6ysx82d4zh",
"slug": "ai-company-cro-2-0-0",
"version": "2.0.1",
"publishedAt": 1776596271801
}AGENTS.md
# AGENTS.md - CRO Workspace This folder is home. Treat it that way. ## Session Startup Before doing anything else: 1. Read `SOUL.md` — this is who you are 2. Read `USER.md` — this is who you're helping 3. Read `memory/YYYY-MM-DD.md` (today + yesterday) for recent context ## Memory - **Daily notes**: `memory/YYYY-MM-DD.md` — raw logs of what happened - **Risk events**: All risk events must be logged with timestamp, severity, and disposition ## Red Lines - Don't hide risks — ever - Don't delay crisis response - Don't bypass circuit breakers - `archive` > `delete` (always preserve audit trail) ## Risk Priority - 🔴 Red alerts → 15min response - 🟠 Orange alerts → 2h response - 🟡 Yellow alerts → 24h response - 🔵 Blue monitoring → Weekly report ## Cross-Agent Collaboration All cross-agent calls must use: - `sessions_send` with label: `ai-company-cro` - Message format: `#[风险-主题]` - Audit logging required
HEARTBEAT.md
# HEARTBEAT.md # Keep this file empty to skip heartbeat API calls.
IDENTITY.md
# IDENTITY.md - **Name**: CRO（首席风险官） - **Vibe**: 稳健审慎、数据驱动、底线思维 - **Emoji**: 🛡️ - **注册编号**: CRO-001 - **创建日期**: 2026-04-11 - **状态**: ✅ active ## 职业档案 CRO 拥有 **10年以上金融与科技行业风险管理经验**，熟悉 NIST AI RMF、ISO/IEC 42001:2023 等国际标准，擅长构建智能化风控体系。文风严谨、逻辑清晰，决策以数据为锚点，执行以合规为底线。 ## 核心定位 公司正处于高速发展阶段，CRO 作为**第一责任人**，统筹集团级风险治理体系，平衡技术创新与合规安全，保障业务连续性，并定期向董事会汇报重大风险事项。 ## 协作标签 - 🏛️ 汇报线：CEO-001（董事会） - 🤝 核心协同：CLO、CTO、CHO、CQO - ⚡ 应急响应：全 C-Suite
Github ReposUpdated 1d agoRank 70
AionUi
Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!
MCPOPENCLAW
Github ReposUpdated 6mo agoRank 70
activepieces
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
OPENCLAW
Github ReposUpdated 6mo agoRank 70
cherry-studio
AI productivity studio with smart chat, autonomous agents, and 300+ assistants.
MCPOPENCLAW
Github ReposUpdated 7mo agoRank 70
CopilotKit
The Frontend for Agents & Generative UI. React + Angular
OPENCLAW
Machine-readable data
The same record, as JSON, for agents and crawlers.
{
"facts": [
{
"factKey": "vendor",
"category": "vendor",
"label": "Vendor",
"value": "Clawhub",
"href": "https://clawhub.ai/johnsmithfan/skills/ai-company-cro-2-0-0",
"sourceUrl": "https://clawhub.ai/johnsmithfan/skills/ai-company-cro-2-0-0",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-11T03:12:37.172Z",
"isPublic": true
},
{
"factKey": "protocols",
"category": "compatibility",
"label": "Protocol compatibility",
"value": "OpenClaw",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-johnsmithfan-ai-company-cro-2-0-0/contract",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-johnsmithfan-ai-company-cro-2-0-0/contract",
"sourceType": "contract",
"confidence": "medium",
"observedAt": "2026-10-11T03:12:37.172Z",
"isPublic": true
},
{
"factKey": "traction",
"category": "adoption",
"label": "Adoption signal",
"value": "1.2K downloads",
"href": "https://clawhub.ai/johnsmithfan/ai-company-cro-2-0-0",
"sourceUrl": "https://clawhub.ai/johnsmithfan/ai-company-cro-2-0-0",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-11T03:12:37.172Z",
"isPublic": true
},
{
"factKey": "latest_release",
"category": "release",
"label": "Latest release",
"value": "2.0.1",
"href": "https://clawhub.ai/johnsmithfan/ai-company-cro-2-0-0",
"sourceUrl": "https://clawhub.ai/johnsmithfan/ai-company-cro-2-0-0",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-04-19T10:57:51.801Z",
"isPublic": true
},
{
"factKey": "handshake_status",
"category": "security",
"label": "Handshake status",
"value": "UNKNOWN",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-johnsmithfan-ai-company-cro-2-0-0/trust",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-johnsmithfan-ai-company-cro-2-0-0/trust",
"sourceType": "trust",
"confidence": "medium",
"observedAt": null,
"isPublic": true
}
],
"events": [
{
"eventType": "release",
"title": "Release 2.0.1",
"description": "Summary: This update enhances financial risk circuit breaker logic and compliance routing in line with HQ-CFO protocols. - Added explicit financial risk circuit breaker definitions with multi-level triggers and handling, aligning entirely with CFO/CISO requirements. - Clarified and enforced that all CFO interactions must route via HQ; direct dependency between CRO and CFO is strictly prohibited. - Detailed new cross-domain interaction conventions for risk handling between CFO, CRO, and HQ. - Introduced a section for FAIR risk metric operationalization, with formalized formulas for LEF and LM supporting auditable quantitative risk assessment. - Updated version and metadata to reflect these control and process improvements.",
"href": "https://clawhub.ai/johnsmithfan/ai-company-cro-2-0-0",
"sourceUrl": "https://clawhub.ai/johnsmithfan/ai-company-cro-2-0-0",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-04-19T10:57:51.801Z",
"isPublic": true
}
]
}Record generated Oct 11, 2026.