Agent skill
share-session
Share Droid sessions as GitHub gists. Use when asked to "share session", "export session to gist", or "create gist from session".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/share-session
SKILL.md
Share Session Skill
Export and share Droid CLI sessions via GitHub gists.
Usage
# List available sessions
./scripts/list.sh
# Share session with auto-generated title
./scripts/share.sh [session-id] "Title for the session"
# Export locally without uploading
node ./scripts/export-html.js <session.jsonl> [output.html]
node ./scripts/export-md.js <session.jsonl> [output.md]
If no session-id provided, uses most recent session.
Auto-naming Sessions
You must generate a title for every session you share.
Instructions:
- Read the session JSONL file to find the first user message
- Generate a short, descriptive title (5-8 words) that captures the main task
- Pass the title as the second argument to share.sh
Title guidelines:
- Be concise and descriptive
- Focus on WHAT was accomplished, not HOW
- No quotes, no special characters
- Examples: "Setting up Cloudflare Tunnel for local dev", "Fix TypeScript build errors in API", "Add dark mode toggle to settings"
./scripts/share.sh "" "Your generated title here"
Formats
- html - Self-contained HTML with syntax highlighting, collapsible tool calls, dark theme
- md - Clean Markdown with collapsible details blocks
- raw - Original JSONL file
Requirements
ghCLI installed and authenticated (gh auth login)- Node.js for HTML/MD export
Session Locations
- Global:
~/.factory/sessions/ - Project-local:
.factory/sessions/
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?