GitHub
skill-improve
Improve existing skills. Triggers include "improve this skill", "skill feels shallow", "upgrade skill", or when self-evaluating skill quality. Codifies the self-eval → research → rewrite → validate pattern.
☆ 0View skill
lnittman AI Skills
GitHub ↗Browse published AI skills maintained by lnittman. Compare skill descriptions and follow each source repository for setup instructions.
Author statistics
Indexed skills
39Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Popular categories
Recent indexing activity
Browse skills
GitHub
fanout
This skill should be used for multi-perspective analysis through parallel copilot sessions. Triggers include "analyze from multiple angles", "what are the gaps/patterns/friction", "explore before deciding", pre...
☆ 0View skill
GitHub
context
Context preservation across sessions, checkpoint monitoring, and agent handoffs. Triggers include "save context", "checkpoint", "hand off", "relay context", or when transitioning between sessions.
☆ 0View skill
GitHub
auto
This skill should be used for autonomous single-repo orchestration. Triggers include "use auto", "autonomous mode", "work on this repo", or when starting a deep work session. LLM ideation discovers work, copilo...
☆ 0View skill
GitHub
skill-compose
This skill should be used when orchestrating multiple skills together for complex workflows. Triggers include "chain these skills", "use X then Y skill", "multi-skill workflow", "which skills", "suggest skills"...
☆ 0View skill
GitHub
issue-context
Enrich issues with intelligent codebase context, architecture diagrams, and agent-ready prompts. Use for preparing issues for implementation or transforming vague tickets into rich specifications.
☆ 0View skill
GitHub
skill-improve
This skill should be used when improving existing Claude Code skills. Triggers include "improve this skill", "skill feels shallow", "upgrade skill", or when self-evaluating skill quality. Codifies the self-eval...
☆ 0View skill
GitHub
emil-kowalski
Design philosophy for UI components, animations, and interactions. Triggers include "make it feel Linear", "emil style", "tasteful animation", or when designing interactive components that need craft and restra...
☆ 0View skill
GitHub
loop
This skill should be used for autonomous work on complex tasks with ZERO context required. Triggers include "start a loop", "work autonomously", "before I sleep", "take this and run with it", or when claude det...
☆ 0View skill
GitHub
pair
This skill should be used for all external AI collaboration - consulting, implementing, or reviewing with codex/copilot. Triggers include "pair with codex", "get a second opinion", "delegate this", "consult on"...
☆ 0View skill
GitHub
metaprompt-factory
This skill should be used when generating structured metaprompts for repeatable tasks. Triggers include "create a metaprompt for X", "generate a review prompt", "make a prompt template", or when building prompt...
☆ 0View skill
GitHub
issue-context
This skill should be used when enriching Linear issues with intelligent codebase context, architecture diagrams, and agent-ready prompts. Use for preparing issues for implementation, transforming vague tickets...
☆ 0View skill
GitHub
project-review
Review current project against mature patterns and standards. Triggers include "review this project", "what am I missing", "align with standards", "check tool usage", or when starting in an unfamiliar project.
☆ 0View skill
GitHub
skill-create
Create or refactor skills, guiding an interactive questionnaire, selecting an archetype (workflow/tool/domain), scaffolding from templates, and validating the result. Triggers include "create skill", "new skill...
☆ 0View skill
GitHub
project-review
This skill should be used for reviewing current project against mature project patterns, tool capabilities, and org standards. Triggers include "review this project", "what am I missing", "align with standards"...
☆ 0View skill
GitHub
skill-compose
Orchestrate multiple skills together for complex workflows. Triggers include "chain these skills", "use X then Y skill", "multi-skill workflow", "which skills", or when a task requires capabilities from several...
☆ 0View skill
GitHub
agent-docs
This skill should be used when the user asks to "audit AGENTS.md", "check agent docs", "verify documentation accuracy", "maintain agent instructions", "check for drift", or mentions documentation needs updating...
☆ 0View skill
GitHub
friction-analysis
Analyze developer experience friction and codebase bottlenecks. Triggers include "analyze friction", "find bottlenecks", "why is development slow", "audit codebase complexity", or "DX review".
☆ 0View skill
GitHub
skill-create
This skill should be used when creating or refactoring Claude Code skills, guiding an interactive questionnaire, selecting an archetype (workflow/tool/domain), scaffolding from templates, and validating the res...
☆ 0View skill
GitHub
ask-deep
This skill should be used for interactive clarification with smart HIL question flows. Triggers include "ask me questions", "help me think through", "what should we consider", session start ("what are we workin...
☆ 0View skill
GitHub
skill-publish
One-way sync from private skills to public versions. Triggers include "publish skills", "sync to public", "update public skills", or when private skills have changed.
☆ 0View skill
GitHub
loop
This skill should be used for autonomous work on complex tasks with ZERO context required. Triggers include "start a loop", "work autonomously", "before I sleep", "take this and run with it", or when claude det...
☆ 0View skill
GitHub
pr-audit
Thorough PR review before merge. Triggers include "review this PR", "audit PR", "is this ready to merge".
☆ 0View skill
GitHub
www-studio
Marketing site development, design system audits, brand page creation, and UI/UX polish. Triggers include "audit www", "polish the marketing site", "add brand page", "design system review", or "make it feel lik...
☆ 0View skill
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.