me.txt
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill is coherent and purpose-aligned, but users should review personal details before publishing and be aware that the optional CLI is an external package run via npx.
This skill appears safe and aligned with its purpose. Before installing or using it, remember that me.txt files are meant to be publicly accessible, so avoid private contact details or sensitive biographical information. If you choose to use the suggested npx CLI, verify the package source first.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Using the optional CLI could execute code from the npm ecosystem; this appears relevant to the skill, but users should trust the package source before running it.
The skill optionally recommends running an external npm package via npx, but no package source, version pin, or install spec is provided in the artifacts.
If the user has a GitHub profile, offer to pre-fill from it using: `npx create-me-txt --github username`
If using the CLI, verify the npm package, prefer a pinned version where possible, and review what it will access before running it.
Personal profile details, contact links, timezone, and preferences may become public and may influence agents that read the file.
The skill creates persistent AI-readable identity context that may be publicly served and reused by agents.
me.txt is an open standard for personal identity files. It's a markdown file at a site root (`yoursite.com/me.txt`) that tells AI agents who someone is.
Only include information intended for public use, review the generated me.txt before publishing, and verify the source of any me.txt fetched from another domain.