Topic: skills
17,247 skills in this topic.
-
ownership-gate
Verify the junior can explain and defend every line of code they wrote. This gate BLOCKS completion if failed.
aiskillstore/marketplace 232
-
performance-fundamentals
Auto-invoke when reviewing loops, data fetching, rendering, database queries, or resource-intensive operations. Identifies N+1 queries, unnecessary re-renders, memory leaks, and scalability issues.
aiskillstore/marketplace 232
-
performance-gate
Verify performance implications were considered and no obvious anti-patterns exist. Issues result in WARNINGS.
aiskillstore/marketplace 232
-
resume-bullet-extraction
Auto-invoke after task completion to generate powerful resume bullet points from completed work.
aiskillstore/marketplace 232
-
security-fundamentals
Auto-invoke when reviewing authentication, authorization, input handling, data exposure, or any user-facing code. Enforces OWASP top 10 awareness and security-first thinking.
aiskillstore/marketplace 232
-
security-gate
Verify security considerations were addressed before shipping. Issues result in WARNINGS that strongly recommend fixing.
aiskillstore/marketplace 232
-
seo-fundamentals
Auto-invoke when reviewing HTML head, meta tags, or Next.js page components. Enforces semantic HTML and search optimization.
aiskillstore/marketplace 232
-
star-story-extraction
Auto-invoke after task completion to extract interview-ready STAR stories from completed work.
aiskillstore/marketplace 232
-
testing-fundamentals
Auto-invoke when reviewing test files or discussing testing strategy. Enforces testing pyramid, strategic coverage, and stack-appropriate frameworks.
aiskillstore/marketplace 232
-
testing-gate
Gate 6 - Verify tests exist and cover critical paths. Issues result in WARNINGS (encourages tests, doesn't block).
aiskillstore/marketplace 232
-
ghe-changelog
This skill should be used when updating the project CHANGELOG, tracking requirement changes, recording design decisions, or documenting version history. Uses git-diff to detect and categorize changes to both code and requirements. Trigger on "changelog", "version history", "what changed", or after significant commits.
aiskillstore/marketplace 232
-
ghe-claim
CLAIM a specific GitHub issue to START working on it. Requires an issue number. Performs validation, atomic claim, posts claim comment, and sets up worktree. Use when user wants to begin work on a specific issue number (e.g., "claim #201", "start working on issue #N").
aiskillstore/marketplace 232
-
ghe-design
Reference material for Athena when writing requirements. NOT a template - Athena writes requirements freely based on the domain. This skill provides guidance patterns that may be useful, not constraints to follow.
aiskillstore/marketplace 232
-
ghe-report
Generate detailed workflow reports with metrics, health assessments, and epic-specific analysis for GitHub Elements. Covers throughput, cycle times, compliance status, and thread history.
aiskillstore/marketplace 232
-
ghe-requirements
This skill should be used when creating, updating, linking, or versioning requirements for GitHub Elements threads. Use when user mentions requirements, specs, REQ files, or when starting feature development. Provides the requirements folder structure, versioning system, and SERENA backup protocols.
aiskillstore/marketplace 232
-
ghe-status
READ-ONLY quick overview of GitHub Elements workflow state. Shows active threads, phase distribution, and workflow health at a glance.
USE WHEN: Asking about status, active threads, workflow state, or needing context at session start.
DO NOT USE WHEN: Claiming issues (use ghe-claim), posting checkpoints (ghe-checkpoint), transitioning phases (ghe-transition), or needing detailed reports (ghe-report).
aiskillstore/marketplace 232
-
ghe-thread-manager
Use this skill when the user expresses ANY intent related to issue/thread management:
- Switching issues: "let's work on X", "switch to #Y", "go to the auth issue"
- Checking status: "what are we working on?", "current issue?", "status?"
- Background work: "what's in background?", "any features ready?", "check progress"
- Starting development: "implement X", "add feature", "fix bug Y", "build a..."
- Joining reviews: "let me see the review", "check that feature", "join #X"
- Pausing/resuming: "pause this", "come back later", "resume #X"
- Stopping transcription: "stop tracking", "don't record this", "private mode"
- Resuming last session: "what were we working on?", "resume last issue", "continue where we left off"
- Any natural expression of wanting to change focus or check work status
This skill interprets natural language - users should NOT memorize commands.
For the full GHE workflow protocol, see skill: github-elements-tracking
aiskillstore/marketplace 232
-
ghe-transition
Change phases in the GitHub Elements workflow by closing current thread and opening the next. Use for DEV→TEST, TEST→REVIEW, REVIEW→merge transitions, or demotions. Do not use for saving progress.
aiskillstore/marketplace 232
-
github-elements-tracking
This skill should be used when the user asks to "track work across sessions", "create an epic", "manage issue waves", "post a checkpoint", "claim an issue", "recover from compaction", "coordinate multiple agents", "update memory bank", "store large documents", or mentions GitHub Issues as persistent memory, multi-session work, context survival, agent collaboration, SERENA MCP memory, or project-level context. Provides complete protocols for using GitHub Issues as permanent memory that survives context exhaustion, with integrated SERENA MCP memory bank for project-level context and large document storage.
aiskillstore/marketplace 232
-
markdown-toc
Use when generating or updating Table of Contents in markdown files. Supports multiple files, glob patterns, configurable header levels, and various insertion modes. Triggered by "generate toc", "update toc", "table of contents", "add toc to markdown".
aiskillstore/marketplace 232
-
marketplace-release
Use when creating releases for Claude Code plugin marketplaces. Supports independent plugin versioning - each plugin can be released separately. Triggered by "release", "bump version", "create release", "publish plugin".
aiskillstore/marketplace 232
-
add-cuda-kernel
Step-by-step tutorial for adding new CUDA kernels to FlashInfer
aiskillstore/marketplace 232
-
benchmark-kernel
Guide for benchmarking FlashInfer kernels with CUPTI timing
aiskillstore/marketplace 232
-
debug-cuda-crash
Tutorial for debugging CUDA crashes using API logging
aiskillstore/marketplace 232