How this skill is triggered — by the user, by Claude, or both
Slash command
/automate:automate-exportThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Arguments: $ARGUMENTS
Arguments: $ARGUMENTS
Read ${CLAUDE_SKILL_DIR}/../../docs/shared-context.md for registry format.
Parse $ARGUMENTS for a file path. Default: ~/.claude/automations-export.json
Read ~/.claude/automations-registry.json. Handle both formats (array and object).
If empty/missing: report "No automations to export." and stop.
For each automation, read its content from the path in the registry.
Create export file:
{
"exportVersion": "1.0",
"exportDate": "YYYY-MM-DD",
"source": "machine-name or user identifier",
"automations": [
{
"name": "icon-prompt",
"type": "skill",
"scope": "global",
"description": "...",
"files": [
{
"relativePath": "SKILL.md",
"content": "--- full file content ---"
}
]
}
]
}
jq . <file> > /dev/null/automate-import <file>"npx claudepluginhub elmisi/claude-code-automation --plugin automateExports skills, templates, or agents from a project to a repository's v0.2 plugin architecture via /agentic-export. Supports dry-run, plugin targeting, and pre-flight checks.
Exports retriever result sets as CSV tables or archives. Invoked via /export or natural language like "save this as a spreadsheet."