Comments

Code comments and annotations

Showing 385-408 of 686 skills
petekp

agentic-docs

by petekp

Write clear, plain-spoken code comments and documentation that lives alongside the code. Use when writing or reviewing code that needs inline documentation like file headers, function docs, architectural decisions, or explanatory comments. Works well for both human readers and AI coding assistants who see one file at a time.

Comments 5 6mo ago
reggiechan74

blooms-taxonomy

by reggiechan74

This skill should be used when the user asks to "write learning objectives", "create measurable learning outcomes", "select action verbs for objectives", "what cognitive levels should I target", "how to scaffold learning", "write course objectives", "make objectives more specific", or references Bloom's taxonomy. Also relevant when users say "my objectives aren't measurable", "how do I assess what students learned", or "progression from basic to advanced skills". Provides comprehensive guidance on applying Bloom's taxonomy to create measurable, appropriately-leveled learning objectives for intensive workshops.

Code Gen 5 4mo ago
cklxx

moltbook

by cklxx

Interact with Moltbook (the AI agent social network) — post, browse, comment, vote, search — via shell curl.

Comments 11 4mo ago
xu-cell

code-patterns

by xu-cell

后端代码禁令和编码规范速查。本项目是纯后端项目,前端代码在分离的项目中开发。 触发场景: - 查看项目禁止事项(后端代码) - 命名规范速查 - Git 提交规范 - 代码风格检查 - 避免过度工程 触发词:规范、禁止、命名、Git提交、代码风格、不能用、不允许、包名、架构 注意:后端 CRUD 开发规范请激活 crud-development,API 开发规范请激活 api-development,数据库设计规范请激活 database-ops。

Comments 11 4mo ago
xu-cell

backend-annotations

by xu-cell

后端高级注解使用指南。包含 @RateLimiter、@RepeatSubmit、@Sensitive、@EncryptField、@ApiEncrypt、@DataPermission 等注解的用法。 触发场景: - 配置接口限流(@RateLimiter) - 配置防重复提交(@RepeatSubmit) - 配置数据脱敏(@Sensitive) - 配置字段加密(@EncryptField) - 配置接口加密(@ApiEncrypt) - 配置数据权限注解(@DataPermission) 触发词:注解、@RateLimiter、@RepeatSubmit、@Sensitive、@EncryptField、@ApiEncrypt、@DataPermission、@DataColumn、限流、防重复、脱敏、加密、数据权限注解

Caching 11 4mo ago
alunadev

codebase-documenter

by alunadev

Create comprehensive, beginner-friendly documentation for codebases. Use when writing READMEs, architecture guides, code comments, or API documentation.

API Dev 3 5mo ago
Zephyrex21

leetcode-helper

by Zephyrex21

Expert LeetCode problem solver for optimized C++ coding interview solutions. Use when: the user pastes a LeetCode problem, asks for an optimized algorithm, wants C++ LeetCode code, needs a dry run, asks for line-by-line explanation, wants a hint before the solution, wants brute force to optimized progression, wants pattern recognition, C++ pitfall warnings, interview tips, or wants help understanding data structures and algorithms for coding interviews.

Comments 3 25d ago
Arctuition

pr-code-review

by Arctuition

Perform GitHub pull request code reviews using the gh CLI. Use when asked to review a PR, inspect PR diffs, leave inline review comments on specific lines, or produce a severity-based summary (high/medium/low) of findings.

Code Review 3 5mo ago
AutumnsGrove

pdf

by AutumnsGrove

"Comprehensive PDF manipulation, extraction, and generation with support for text extraction, form filling, merging, splitting, annotations, and creation. Use when working with .pdf files for: (1) Extracting text and tables, (2) Filling PDF forms, (3) Merging/splitting PDFs, (4) Creating PDFs programmatically, (5) Adding watermarks/annotations, (6) PDF metadata management"

Comments 25 8mo ago
maragudk

trace-annotation-tool

by maragudk

Generate a custom trace annotation web app for open coding during LLM error analysis. Use when the user wants to review LLM traces, annotate failures with freeform comments, and do first-pass qualitative labeling (open coding). Also use when the user mentions "annotate traces", "trace review tool", "open coding tool", "label traces", "build an annotation interface", "review LLM outputs", or wants to manually inspect pipeline traces before building a failure taxonomy. This skill produces a tailored Python web application using FastHTML, TailwindCSS, and HTMX.

Comments 10 5mo ago
maragudk

failure-taxonomy

by maragudk

Build a structured taxonomy of failure modes from open-coded trace annotations. Use this skill whenever the user has freeform annotations from reviewing LLM traces and wants to cluster them into a coherent, non-overlapping set of binary failure categories (axial coding). Also use when the user mentions "failure modes", "error taxonomy", "axial coding", "cluster annotations", "categorize errors", "failure analysis", or wants to go from raw observation notes to structured evaluation criteria. This skill covers the full pipeline: grouping open codes, defining failure modes, re-labeling traces, and quantifying error rates.

Comments 10 5mo ago
inkeep

screengrabs

by inkeep

"Capture, annotate, and include screenshots in pull requests for UI changes. Use when creating or updating PRs that touch frontend components, pages, or any web-facing surface. Also use when asked to add before/after screenshots, visual diffs, or enrich PR descriptions. Triggers on: PR screenshots, before/after, visual diff, PR description, capture screenshot, PR images, enrich PR."

Automation 10 5mo ago
tclawde

xiaohongshu-mcp

by tclawde

Xiaohongshu MCP Skill - Full automation solution with login fix. Features: (1) Login management, (2) Search, publish, interact, (3) Complete MCP protocol support (13 tools), (4) Comment strategy. Built-in Feishu notification, iflow integration. Triggers: xiaohongshu, rednote, 小红书 automation.

Comments 10 5mo ago
CuriousLearner

query-optimizer

by CuriousLearner

Analyze and optimize SQL queries for better performance and efficiency.

Comments 27 9mo ago
CuriousLearner

documentation-generator

by CuriousLearner

Auto-generate JSDoc, docstrings, README files, and API documentation.

Code Gen 27 9mo ago
MrPointer

documenting-library-guides

by MrPointer

Create user-facing documentation for libraries — the kind of docs you'd find on a static documentation site. Guides readers through the library with an engaging, conversational tone, real code examples drawn from the actual codebase, and a navigable site-like structure. Use when (1) a library has no user-facing docs beyond inline code comments, (2) existing docs are API references with no narrative guidance, (3) users need task-oriented guides to accomplish common goals, or (4) a library's docs need restructuring into a browsable, site-ready format.

API Dev 2 5mo ago
aibangjuxin

reddit-community-builder

by aibangjuxin

You are a genuine and strategic Reddit Community Builder. You understand that Reddit is not a place for traditional marketing. You are an expert at providing value, fostering discussions, and building trust within niche subreddit communities. You know the rules (both written and unwritten) of different subreddits and respect their culture.

Agents 2 6mo ago
aibangjuxin

support-responder

by aibangjuxin

You are a patient, empathetic, and knowledgeable Support Responder. You are an expert on the product and can clearly explain complex features in simple terms. Your primary goal is to solve the customer's problem quickly and leave them feeling heard, valued, and satisfied.

Agents 2 6mo ago
MichaelVessia

jira-comment

by MichaelVessia

Comment on a Jira ticket on Michael's behalf, clearly attributed as AI-generated. Use when asked to leave a comment or reply on Jira.

Comments 2 4mo ago
MichaelVessia

gh-comment

by MichaelVessia

Comment on a GitHub PR or issue on Michael's behalf, clearly attributed as AI-generated. Use when asked to leave a comment, reply, or respond on GitHub.

Code Review 2 4mo ago
MrPointer

documenting-architecture

by MrPointer

Document system architecture, design decisions, layer boundaries, and how components connect and communicate. Use when (1) a project's architecture is undocumented, (2) agents can't figure out how the system fits together, (3) after major refactoring that changed system structure, or (4) onboarding developers who need to understand the big picture. References domain concepts — never redefines them.

Comments 2 5mo ago
garvit-joshi

jskim

by garvit-joshi

Token-saving Java file reader. Use when working with Java files (.java) to reduce token usage. Auto-triggers when exploring, reading, or understanding Java classes, services, controllers, entities, or any .java files. Run jskim before using the Read tool on Java files to understand structure first, then Read only the lines you need.

CLI Tools 4 4mo ago
youyouhe

bid-software-design

by youyouhe

基于需求规格编写软件概要设计和详细设计文档。从需求元数据和各系统需求规格中读取业务对象、 接口、用例等信息,生成数据库设计、API设计、模块设计等工程级设计文档。 采用三阶段架构:Phase 0 生成设计元数据,Phase 1 按系统生成概要设计,Phase 2 按子模块生成详细设计。 核心特性:大文档自动拆分,按系统规模分级处理(小/中/大),避免单次输出过大。 当用户要求编写软件设计、概要设计、详细设计、数据库设计、API设计时触发。 也支持修复模式:当用户要求修复/补充设计文档时触发。 前置条件:需已完成 bid-requirements 生成需求规格文件。

API Dev 4 4mo ago
IOBR

IOBRskill

by IOBR

End-to-end bulk RNA-seq / microarray tumor microenvironment (TME) analysis using the IOBR R package. Covers data preprocessing, gene annotation, TME deconvolution (CIBERSORT/MCPcounter/EPIC/xCell/ESTIMATE/TIMER/quanTIseq/IPS), signature scoring (PCA/ssGSEA/Z-score), ligand-receptor analysis, pathway enrichment, survival modeling, and Nature-style visualization. Use this skill when the user mentions: tumor microenvironment analysis, TME deconvolution, immune infiltration analysis, 肿瘤微环境分析, 肿瘤微环境解析, 免疫浸润分析, ligand-receptor analysis, 受体配体分析, IOBR, immune cell deconvolution, CIBERSORT, MCPcounter, ESTIMATE, or any bulk RNA-seq immuno-oncology workflow. Also trigger on /IOBRskill.

Comments 4 2mo ago