How do I install the Akf Trust Metadata skill?

Run npx skillmds@latest add anhvu1107/akf-trust-metadata in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Akf Trust Metadata safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Akf Trust Metadata?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Akf Trust Metadata free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Akf Trust Metadata?

anhvu1107 (@anhvu1107) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Akf Trust Metadata by anhvu1107 — Agent Skill

Name: Akf Trust Metadata
Author: anhvu1107

Akf Trust Metadata

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.

anhvu1107 a8c31d0 6 files · 6.6 KB Updated Sep 17, 2026

File contents

AKF — The AI Native File Format

Selective Reading Rule

Start with:

references/senior-master-standard.md
references/usage-routing.md
references/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>          # 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 confidential for finance/secret/internal paths
--label public for README, docs, examples
Default: internal

Install

pip install akf

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.

---name: akf-trust-metadatadescription: 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 RuleStart with:- `references/senior-master-standard.md`- `references/usage-routing.md`- `references/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 UseUse 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```bashakf 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```bashakf read <file> # Check existing trust metadataakf inspect <file> # See detailed trust scores```## Compliance auditing```bashakf audit <file> --regulation eu_ai_act # EU AI Act Article 50akf audit <file> --regulation hipaa # HIPAAakf audit <file> --regulation sox # SOXakf 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```bashpip 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.

Frequently asked questions