Ai Company Standardization
v1.0.0AI Company 标准化流程 Skill — 将任意 Skill 转换为 ClawHub Schema v1.0 合规标准。包含 Frontmatter 审计、内容结构规范、Schema 合规检查、接口标准化、质量门五步流程。
⭐ 0· 46·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The skill's name/description (standardizing skills to ClawHub Schema v1.0) match the actions described in SKILL.md: auditing frontmatter, validating schema, and rewriting files. Declared dependency on a vetter skill is reasonable. The SKILL.md includes an explicit permissions declaration to read/write skills/, which is appropriate for a standardizer.
Instruction Scope
The runtime instructions explicitly direct reading and modifying files under a target skill directory (audit_frontmatter, schema checks, rewriting frontmatter/modules). This stays within the stated purpose, but it does grant the skill authority to modify arbitrary skill files (especially when force_rewrite=true). The SKILL.md also prescribes checks to avoid hardcoded org data and undisclosed network calls, which is good practice.
Install Mechanism
No install spec and no code files — instruction-only. This minimizes installer risk because nothing is downloaded or written by an installer step.
Credentials
No environment variables, credentials, or external networks are required. The only requested permission is file read/write for skills/, which is proportional to a tool designed to modify skill content.
Persistence & Privilege
always:false (not force-included). However, the skill is allowed to modify files under skills/, which is a sensitive capability: an automated rewrite could introduce unintended changes to other skills. Autonomous invocation is permitted (disable-model-invocation:false) — this is the platform default but combined with file-write capability means you should restrict when/how it is used (use dry-run and manual review).
Assessment
This skill appears to do what it says: audit and standardize other skills' frontmatter and structure. Key things to consider before installing or enabling it broadly:
- It needs write access to your skills/ directory and can modify files. Use dry_run and inspect the dry-run report before allowing force_rewrite or automatic runs.
- Backup or put your skills under version control so you can review and revert any automated edits.
- Verify the skill source and trustworthiness (homepage and owner). The registry metadata and SKILL.md appear coherent, but the source is 'unknown' in the listing you provided.
- Check the dependent skill (skill-vetter) to ensure it is trusted and won't introduce unexpected behavior.
- Prefer enabling this skill for manual/invoked runs initially rather than granting it unattended autonomous access across all agents.
If you want, I can draft a short checklist of safe pre-conditions and a sample dry-run review procedure you can use before applying changes.Like a lobster shell, security has layers — review code before you run it.
latestvk97abhe75vstzfd1kcbvyzg6a984rakc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.