Topic: skills
17,247 skills in this topic.
-
codex-test-review
Review test case sufficiency using Codex MCP, suggest additional edge cases. Supports review loop with context preservation.
sd0xdev/sd0x-dev-flow 139
-
review-spec
Review technical spec documents from completeness, feasibility, risk, and code consistency perspectives.
sd0xdev/sd0x-dev-flow 139
-
codex-review-doc
Review documents using Codex MCP. Supports review loop with context preservation.
sd0xdev/sd0x-dev-flow 139
-
create-request
Create, update, or scan per-task request tickets for progress tracking. These are date-prefixed non-lifecycle docs under requests/, NOT feature-level requirements (use /req-analyze for those). Use when: tracking task progress, updating completion status, scanning incomplete requests, checking request status dashboard. Not for: feature-level problem-space analysis (use req-analyze for 1-requirements.md lifecycle doc), tech specs (use tech-spec), code implementation (use feature-dev). Output: request ticket with status tracking, referencing parent tech-spec.
sd0xdev/sd0x-dev-flow 139
-
architecture
Architecture design and documentation. Produces 3-architecture.md with component diagrams, data flow, integration points, and architecture decisions. Reads existing tech-spec as input. Use when: designing system architecture, documenting component interactions, creating architecture docs, producing 3-architecture.md. Not for: tech spec writing (use tech-spec), code implementation (use feature-dev), architecture consulting only (use codex-architect).
sd0xdev/sd0x-dev-flow 139
-
install-scripts
Install plugin runner scripts into project .claude/scripts/ for persistent use without plugin loaded
sd0xdev/sd0x-dev-flow 139
-
post-dev-test
Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.
sd0xdev/sd0x-dev-flow 139
-
pr-comment
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review. Use when: posting code review comments, giving PR feedback, sending inline suggestions. Not for: reading existing reviews (use load-pr-review), creating PRs (use create-pr), PR status (use pr-summary).
sd0xdev/sd0x-dev-flow 139
-
test-health
Holistic test coverage measurement. Use when: assessing test health, measuring coverage trends, quantitative + qualitative test audit. Not for: running tests (use verify), reviewing test sufficiency only (use codex-test-review), generating tests (use codex-test-gen). Output: multi-dimensional dashboard with coverage metrics + test inventory + trend.
sd0xdev/sd0x-dev-flow 139
-
dev-security-audit
Comprehensive developer workstation security audit — scans for exposed credentials, compromised application data, persistence mechanisms, and supply chain attack indicators. Use this skill whenever the user suspects their machine may be compromised, wants to check for exposed secrets, asks about supply chain attacks, or wants a full security audit of their development environment. Also triggers on: 'am I compromised', 'check my security', 'scan for leaked keys', 'credential audit', 'supply chain attack', 'supply chain check', 'check if I was hacked'.
sd0xdev/sd0x-dev-flow 139
-
codex-security
OWASP Top 10 security review using Codex MCP. Supports review loop with context preservation.
sd0xdev/sd0x-dev-flow 139
-
install-hooks
Install plugin hooks into project .claude/ for persistent use without plugin loaded
sd0xdev/sd0x-dev-flow 139
-
smart-commit
Smart batch commit. Analyzes uncommitted changes, groups by cohesion, generates commit messages matching project style. Default: output git commands for manual execution. With --execute: directly run git add + git commit (requires user approval). Use when: user says 'commit', 'batch commit', 'prepare commit', 'write commit message', or /smart-commit
sd0xdev/sd0x-dev-flow 139
-
skill-health-check
Validate skill quality against routing, progressive loading, and verification criteria. Use when: auditing skills, checking skill health, reviewing skill design. Not for: code review (use codex-code-review) or doc review (use doc-review). Output: health report with per-skill ratings + Gate.
sd0xdev/sd0x-dev-flow 139
-
ddia-principles
Designing Data-Intensive Applications (DDIA) distilled reference guide by Martin Kleppmann. MUST be loaded when: designing database schemas, choosing storage engines, implementing replication or partitioning, handling distributed transactions, building batch/stream processing pipelines, choosing consistency models, implementing consensus, designing data flow architectures, evaluating trade-offs between availability and consistency, encoding/serialization decisions, data modeling (relational vs document vs graph), building fault-tolerant systems, or any system design and architecture discussion involving data-intensive applications. Trigger on: database design, replication, partitioning, sharding, transactions, isolation levels, consistency, consensus, CAP theorem, batch processing, stream processing, MapReduce, Kafka, event sourcing, CDC, OLTP, OLAP, B-tree, LSM-tree, data warehouse, schema evolution, encoding formats, distributed systems, fault tolerance, leader election, quorum.
luoling8192/ai-coding-principles 145
-
ai-coding-discipline
Mandatory coding discipline rules that prevent common AI coding anti-patterns. MUST be loaded for ALL code writing, editing, reviewing, bug fixing, and testing tasks. Trigger on: writing code, editing code, fixing bugs, writing tests, implementing features, refactoring, code review, creating functions, adding error handling, debugging. This skill enforces fail-fast principles, proper error propagation, meaningful tests, and disciplined debugging workflows. Always active when Claude writes or modifies code.
luoling8192/ai-coding-principles 145
-
obsidian
Comprehensive guidelines for Obsidian.md plugin development including all 27 ESLint rules from eslint-plugin-obsidianmd v0.1.9, TypeScript best practices, memory management, API usage (requestUrl vs fetch), UI/UX standards, locale file sentence-case enforcement, and submission requirements. Use when working with Obsidian plugins, main.ts files, manifest.json, Plugin class, MarkdownView, TFile, vault operations, or any Obsidian API development.
gapmiss/obsidian-plugin-skill 119
-
Log Analyzer
智能日志分析工具，帮助快速定位应用错误和性能瓶颈
huifer/skill-security-scan 117
-
Data Optimizer Pro
智能数据优化工具，自动清理和优化项目文件
huifer/skill-security-scan 117
-
Log Analyzer
智能日志分析工具，帮助快速定位应用错误和性能瓶颈
huifer/skill-security-scan 117
-
harness-engineering-guide
Audit, design, and implement AI agent harnesses for any codebase. A harness is the constraints, feedback loops, and verification systems surrounding AI coding agents — improving it is the highest-leverage way to improve AI code quality. Three modes: Audit (scorecard), Implement (set up components), Design (full strategy). Use whenever the user mentions harness engineering, agent guardrails, AI coding quality, AGENTS.md, CLAUDE.md setup, agent feedback loops, entropy management, AI code review, vibe coding quality, harness audit, harness score, AI slop, agent-first engineering. Also trigger when users want to understand why AI agents produce bad code, make their repo work better with AI agents, set up CI/CD for agent workflows, design verification systems, or scale AI-assisted development. Proactively suggest when discussing AI code drift or controlling AI-generated code quality.
OdradekAI/harness-engineering-guide 130
-
customer-success-playbook
Use this skill when building health scores, predicting churn, identifying expansion signals, or running QBRs. Triggers on customer success, health scores, churn prediction, expansion signals, customer QBRs, onboarding playbooks, NRR optimization, and any task requiring customer success strategy or operations.
AbsolutelySkilled/AbsolutelySkilled 116
-
ai-agent-design
Use this skill when designing AI agent architectures, implementing tool use, building multi-agent systems, or creating agent memory. Triggers on AI agents, tool calling, agent loops, ReAct pattern, multi-agent orchestration, agent memory, planning strategies, agent evaluation, and any task requiring autonomous AI agent design.
AbsolutelySkilled/AbsolutelySkilled 116
-
competitive-analysis
Use this skill when analyzing competitive landscapes, comparing features, positioning against competitors, or conducting SWOT analysis. Triggers on competitive analysis, market landscape, feature comparison, SWOT, competitor positioning, market mapping, and any task requiring competitive intelligence or strategic positioning.
AbsolutelySkilled/AbsolutelySkilled 116