| name | akf-trust-metadata |
| description | ALWAYS use this when the user mentions AKF Trust Metadata, asks to build, debug, review, document, automate, test, configure, migrate, or make decisions in this domain, or the task clearly depends on AKF Trust Metadata; scope: The AI native file format. Apply the bundled workflow, references, scripts, Senior Master standard, and Codex strict review gate before final output. |
AKF — The AI Native File Format
Selective Reading Rule
Start with:
references/senior-master-standard.mdreferences/usage-routing.mdreferences/quality-checklist.md
Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.
Every photo has EXIF. Every song has ID3. AKF is the native metadata format for AI-generated content.
When to Use
Use this skill when you need to stamp, inspect, or audit provenance and trust metadata on AI-generated or AI-modified files for compliance, review, or handoff workflows.
After creating or modifying files
akf stamp <file> --agent <agent-name> --evidence "<what you did>"
Evidence examples:
- "generated from user prompt"
- "refactored existing code"
- "tests pass"
- "docs reviewed"
Before modifying existing files
akf read <file>
akf inspect <file>
Compliance auditing
akf audit <file> --regulation eu_ai_act
akf audit <file> --regulation hipaa
akf audit <file> --regulation sox
akf audit <file> --regulation nist_ai
Classification
--label confidential for finance/secret/internal paths--label public for README, docs, examples- Default:
internal
Install
pip install akf
Links
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
