← LeaderboardThe Skill Leaderboard

akf-trust-metadata

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.

Published by sickn33 ↗sickn33/agentic-awesome-skills

Try your first task

akf-trust-metadata

Start a fresh conversation. Replace the highlighted placeholders.

Use akf-trust-metadata to inspect and audit provenance and trust metadata for [files], producing a compliance-review report with gaps and recommended metadata updates.

Required inputs

  • [files]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: akf-trust-metadatadescription: "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."risk: criticalsource: communitydate_added: "2026-03-27"author: HMAKT99tags: - trust- metadata- provenance- compliance- file-format- ai-native

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.

Scope and Evidence

Use a reviewed, project-pinned installation; inspect the installed CLI help before using version-dependent flags. Stamping modifies files: confirm the target scope, preserve originals and verify metadata plus content integrity afterward. Trust scores and labels are declarations, not independent proof of accuracy or legal compliance. Never stamp “tests pass” unless the actual named checks passed for the exact artifact. Keep confidential data out of metadata that may travel with shared files.

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

Advisory Metadata Checks

The following upstream-style command examples inspect metadata fields. Their output cannot certify regulatory compliance; verify applicability and requirements separately.

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 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.