Akf trust metadata
Skill sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills/skills/akf-trust-metadata
AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 1,987+ agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.
npx -y skills add sickn33/agentic-awesome-skills --skill akf-trust-metadataAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing.
SKILL.md
1.9 KB, as published. Nobody here has run it
AKF — The AI Native File Format
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> # Check existing trust metadata
akf inspect <file> # See detailed trust scores
Compliance auditing
akf audit <file> --regulation eu_ai_act # EU AI Act Article 50
akf audit <file> --regulation hipaa # HIPAA
akf audit <file> --regulation sox # SOX
akf audit <file> --regulation nist_ai # NIST AI RMF
Classification
--label confidentialfor finance/secret/internal paths--label publicfor README, docs, examples- Default:
internal
Install
pip install akf
Links
- https://akf.dev
- https://github.com/HMAKT99/AKF
- npm:
npm install akf-format
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.