All categories
Documentation
Docs, README files, API references, tutorials, specs, and changelogs
- 15,637
- 652
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse documentation skills
Showing 14,065–14,088 of 15,637 skills
- Leverage Point AuditAudit a codebase for the 12 leverage points of agentic coding. Identifies gaps and provides prioritized recommendations. Use when improving agentic coding capability, analyzing why agents fail, or optimizing a codebase for autonomous work.Votes: 0GitHub stars: 666
- LettaLetta framework for building stateful AI agents with long-term memory. Use for AI agent development, memory management, tool integration, and multi-agent systems.Votes: 0GitHub stars: 666
- LetaFast semantic code navigation via LSP. Load FIRST before ANY code task - even 'simple' ones. Trigger scenarios: (1) fixing lint/type/pyright/mypy warnings or errors, (2) fixing reportAny/reportUnknownType/Any type errors, (3) adding type annotations, (4) refactoring or modifying code, (5) finding where a function/class/symbol is defined, (6) finding where a symbol is used/referenced/imported, (7) understanding what a function calls or what calls it, (8) exploring unfamiliar code or understand...Votes: 0GitHub stars: 666
- Lesson GeneratorGenerate lesson content following 4-Layer Teaching Framework with standardized metadata and Docusaurus conventionsVotes: 0GitHub stars: 666
- Legacy StateStandards for State integration with Views using Coroutines and LifecycleVotes: 0GitHub stars: 666
- Leavn Ops ReleaseUse this skill when preparing releases, generating changelogs, or creating release announcements.Votes: 0GitHub stars: 666
- Learnings LogHistorical record of expert tips and learnings that have been integrated into the plugin skills. Consult this when patterns emerge or to understand the evolution of knowledge.Votes: 0GitHub stars: 666
- Learning ObjectivesGenerate measurable learning outcomes aligned with Bloom's taxonomy and CEFR proficiency levels for educational content. Use when educators need to define what students will achieve, create learning objectives for curriculum planning, or ensure objectives are specific and testable rather than vague.Votes: 0GitHub stars: 666
- Learning Help SystemDesign context-sensitive help systems, tooltips, onboarding flows, and support documentation for learning platforms. Use for user assistance. Activates on "help system", "user assistance", "onboarding", or "contextual help".Votes: 0GitHub stars: 666
- Learning Faq GeneratorGenerate comprehensive FAQs from common learner questions, analytics, discussion forums, and support tickets. Use for self-service support. Activates on "FAQ", "common questions", "help documentation", or "student support".Votes: 0GitHub stars: 666
- Learning Design ReviewReview educational content against the Four Learning Design Pillars framework. Use when users want to evaluate course materials, lessons, tutorials, e-learning modules, or any instructional content for alignment with evidence-based learning design principles. Provides structured feedback with specific principle references (e.g., 1.1.1, 2.3.4) and actionable recommendations.Votes: 0GitHub stars: 666
- Learning Design ChecklistGenerate a quick compliance checklist from the Four Learning Design Pillars. Use when users want a practical checklist for reviewing content, a quick audit tool, or verification questions for specific pillars.Votes: 0GitHub stars: 666
- Learned DocsThis skill should be used when writing, modifying, or reorganizingVotes: 0GitHub stars: 666
- Learn SkillsLearn how Nexus skills work. Load when user mentions: learn skills, how do skills work, what is a skill, skill tutorial, skill structure, understand skills, explain skills, when to create skill, skill vs project. 10-12 min.Votes: 0GitHub stars: 666
- Learn Skill会話履歴や作業内容から、再利用可能なエージェントスキルを生成または追記するVotes: 0GitHub stars: 666
- Learn NexusMaster Nexus philosophy and best practices. Load when user mentions: learn nexus, nexus tutorial, system mastery, nexus best practices, how nexus works, nexus philosophy, nexus design, understand nexus, nexus deep dive. 15-18 min.Votes: 0GitHub stars: 666
- Lead EngineerUse for implementing features, writing production TypeScript/Langium code, code review guidance, and ensuring technical quality. Activate when implementing new functionality, reviewing PRs, or optimizing performance.Votes: 0GitHub stars: 666
- Lcp Wysiwid SpecWrite WYSIWID-style design docs (Concepts + Synchronizations) for go-lcpd, keeping terminology consistent with code.Votes: 0GitHub stars: 666
- Lcp RepoRepository orientation and which Codex skills to use for each area (go-lcpd, protocol spec, docs, openai-serve, ExecPlans).Votes: 0GitHub stars: 666
- Lcp Protocol SpecEdit LCP protocol docs under docs/protocol/ in BOLT-style (TLVs, message formats, state flow).Votes: 0GitHub stars: 666
- Layout DesignerDesigns page layouts, grid systems, and structural arrangements. Use when creating layouts for pages, sections, or components. Considers responsive design, visual hierarchy, and accessibility.Votes: 0GitHub stars: 666
- Law Machine Readable InterpreterInterprets legal text in regelrecht YAML files and generates machine-readable execution logic with parameters, operations, outputs, and cross-law references. Use when user wants to make a law executable, add machine_readable sections, or interpret legal articles for computational execution.Votes: 0GitHub stars: 666
- LaunchpadInteract with Canonical's Launchpad platform via the Launchpad API (api.launchpad.net) using the lp-api CLI tool. Use when working with Ubuntu/Debian packages, bugs, builds, people, projects, or any Launchpad API resources. Triggered by mentions of Launchpad API, Ubuntu development, package builds, or bug tracking.Votes: 0GitHub stars: 666
- Latex WritingGuide LaTeX document authoring following best practices and proper semantic markup. Use proactively when: (1) writing or editing .tex files, (2) writing or editing .nw literate programming files, (3) literate-programming skill is active and working with .nw files, (4) user mentions LaTeX, BibTeX, or document formatting, (5) reviewing LaTeX code quality. Ensures proper use of semantic environments (description vs itemize), csquotes (\enquote{} not ``...''), and cleveref (\cref{} not \S\ref{}).Votes: 0GitHub stars: 666