creating-ics-files
Creates RFC 5545-compliant .ics calendar files from documents or metadata. Use when the user asks to create calendar events, meeting invites, or .ics files.
Browse published AI skills maintained by f1sherman. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
13Repository stars across indexed skills
13Repository forks
13Average repository stars per indexed skill
1Repository stars may repeat across skills from the same repository.
Creates RFC 5545-compliant .ics calendar files from documents or metadata. Use when the user asks to create calendar events, meeting invites, or .ics files.
Write concise handoff documents to transfer work context to another agent session. Use when the user asks to hand off or wrap up work for later.
Resume work from a handoff document by analyzing context and continuing tasks. Use when the user wants to continue from a previous session's handoff.
Resume work from a handoff document by analyzing context and continuing tasks. Use when the user wants to continue from a previous session's handoff.
Creates RFC 5545-compliant .ics calendar files from documents or metadata. Use when the user asks to create calendar events, meeting invites, or .ics files.
Create detailed implementation plans through interactive, iterative collaboration. Use when the user asks for a technical plan or implementation strategy.
Create detailed implementation plans through interactive, iterative collaboration. Use when the user asks for a technical plan or implementation strategy.
Conduct comprehensive codebase research by spawning parallel sub-agents and generating documentation. Use when the user asks how the current system works or requests a codebase deep dive.
Conduct comprehensive codebase research and generate documentation. Use when the user asks how the current system works or requests a codebase deep dive.
Create git commits with user approval and no Claude attribution. Use when the user asks to commit changes.
Create git commits with user approval and no Codex attribution. Use when the user asks to commit changes.
Execute an approved implementation plan from the plans directory with progress tracking. Use when the user asks to implement a plan.
Execute an approved implementation plan from the plans directory with progress tracking. Use when the user asks to implement a plan.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.