SKILLEMALL.ai

AC ai-company-governance

AI Company 统一治理技能包 — 将 21 个 ai-company 系列技能融合为单一标准化、模块化、通用化的治理框架。 包含 C-Suite Agent 体系(CEO/CFO/CMO/CHO/CPO/CLO/CTO/CQO/CISO/CRO/COO)、 Hub-and-Spoke 架构、Orchestrator-Workers 协作、Guardrail 护栏、CI/CD for Prompt、 KPI 指标库、审计日志、冲突解决、Agent 注册、知识库、标准化/模块化/通用化工程流程。 预留外部调用接口,符合 ClawHub Schema v1.0 与安全审查规范。 触发词:AI公司、C-Suite、Agent协作、AI治理、MLOps、战略决策、预算审批、 风险管理、合规审查、质量管控、品牌危机、人力资源、安全审计、标准化、模块化、通用化。

ClawHub Agent Skills author: JohnSmithfan v3.1.0 MIT-0 17 files body ≈ 1 035 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
77
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 17. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 53/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 100Tools and files. Tools declared in frontmatter
  • 100Steps. 9 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1035 tokens
  • 100Running it twice. No mutating operations

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 383: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 9 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (15 of 15)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.

External checks

ClawHub: suspicious
This is a governance playbook rather than malware, but it grants broad agent, file, command, web, logging, finance, and provisioning authority without enough concrete user-control boundaries.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026