Manage cross-agent skill files from Obsidian with Agentfiles
Use Agentfiles when an operator wants to browse, create, edit, install, and audit skills, commands, agents, rules, memories, and coding-session artifacts across multiple AI coding tools from Obsidian.
npx skills add agentskillexchange/skills --skill manage-cross-agent-skill-files-from-obsidian-with-agentfiles
Use Agentfiles when an operator maintains reusable agent instructions across several coding assistants and wants one desktop workspace for those files. The workflow installs the Obsidian community plugin, lets it read supported agent directories, then uses Obsidian to browse, search, create, edit, preview, and save skills, commands, agents, rules, memories, marketplace installs, and Claude Code conversation exports.
What this skill actually does
Invoke it instead of editing each tool’s config folders by hand when the job is agent-file inventory, cleanup, creation, or cross-tool reuse. The scope boundary is local agent-file management through the Obsidian plugin and optional skillkit analytics; it is not a generic Obsidian note-taking entry, an AI coding framework, or a marketplace listing. The agent/operator actually keeps agent artifacts organized, reviewable, and installable across supported hosts.
Inputs and prerequisites: Obsidian desktop with Community plugins enabled; local agent directories for supported hosts; optional @crafter/skillkit CLI for usage analytics.
Setup notes: Install from Obsidian with obsidian://show-plugin?id=agentfiles or search for Agentfiles under Settings > Community plugins. For manual install, download main.js, manifest.json, and styles.css from the latest release, place them in /.obsidian/plugins/agentfiles/, and enable the plugin. Optionally install analytics with npm i -g @crafter/skillkit and run skillkit scan.
Source and verification boundary: use https://agentfiles.crafter.run as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.