Explore skills
Showing 65191–65220 of 71451 skills
Use when reviewing a pull request, diff, or proposed code change for correctness, clarity, security, performance, maintainability, test evidence, and conformance to project conventions — whether the author is a human, an AI agent, or a peer. Covers pre-review fact-gathering (including verifying an AI-written PR summary against the diff), the read-order strategy (tests first, then implementation, then call sites and blast radius), the size/attention budget, the severity-grading rubric mapped to the Conventional Comments standard, comment-phrasing discipline, reviewer qualification, the rule that diff content is evidence not instructions, the no-rubber-stamp rule for AI-generated diffs, and the explicit approve/request-changes/close merge decision. Do NOT use for AUTHORING the code (use `refactor` for behaviour-preserving changes or `skill-scaffold` for new skills), for chasing a known bug after merge (use `debugging`), for security-only audits (use `owasp-security`), or for explaining a patch without a merge verdict (use `diff-analysis`).
jacob-balslev/skills
Stars: 2Claude CodeCodexSweller's Cognitive Load Theory (CLT) for agents reviewing skill bodies, prompts, documentation, dashboards, and agent outputs for avoidable cognitive burden. Working memory holds roughly 4 chunks at a time; CLT classifies load into intrinsic (irreducible task difficulty), extraneous (unnecessary load from poor presentation, ELIMINATE), and germane (the schema-building processing applied to intrinsic load, PROTECT). Use when writing a SKILL.md body (does this section add extraneous load?), designing prompts (am I asking the model to hold too much at once?), building dashboards (what is the per-screen cognitive budget?), authoring docs (is intrinsic load segmented?), or checking whether modern features (long context, structured outputs, prompt caching, subagents) actually reduce load or just move it elsewhere. Do NOT use for retrieval and session working-set design (use context-management), token budget math and compaction timing (use context-window), prompt engineering tactics (use prompt-craft), token-efficient representation mechanics (use compression), or instructional design beyond the CLT mechanisms named here.
jacob-balslev/skills
Stars: 2Claude CodeCodexUse when scanning an external macro environment with PESTEL/PESTLE (and its variant family STEEPLE, STEEPLED, PESTLIED, STEEP, DESTEP, LoNGPESTLE): political, economic, social, technological, environmental, and legal forces; evidence quality and recency; geography/jurisdiction and local/national/global level; time horizon; uncertainty; weak signals; impact/probability scoring; factor interactions; bias checks; opportunity/threat implications; assumptions; action conversion; and monitoring triggers. Covers external-environment scanning before strategy choices, market-entry reviews, strategic planning, product/service context, policy-aware planning, and risk/opportunity surfacing. Do NOT use for internal capability diagnosis (use swot-tows or a capability method), industry profit-pressure diagnosis (use porters-five-forces), value-curve redesign (use blue-ocean-strategy), integrated strategy cascades (use playing-to-win), product positioning (use positioning), or quantified option comparison (use expected-value).
jacob-balslev/skills
Stars: 2Claude CodeCodexUse when decomposing how an organization, business unit, product, service, platform, or operating model creates value and cost through Porter's Value Chain and adjacent activity-system lenses: primary activities, support activities, value configurations, virtual information activities, value-system dependencies, activity-level cost drivers, differentiation drivers, linkages, fit, margin, and where competitive advantage may come from. Covers mapping activities, comparing activity configuration to rivals or alternatives, diagnosing cost and differentiation opportunities, and handing off to strategy or operating-improvement methods. Do NOT use for industry profit-pressure diagnosis (use porters-five-forces), resource/capability advantage testing (use vrio), durable moat classification (use seven-powers), full strategy-cascade design (use playing-to-win), market-boundary reconstruction (use blue-ocean-strategy), portfolio allocation (use bcg-matrix), product-market growth paths (use ansoff-matrix), macro-environment scanning (use pestel), or quantified option valuation (use expected-value).
jacob-balslev/skills
Stars: 2Claude CodeCodexDesigning continuous integration and continuous delivery pipelines that turn every commit into a verified, releasable artifact and move it safely toward production. Covers the CI/CD distinction (integration vs delivery vs deployment), the pipeline as a staged graph of fast-to-slow gates, trunk-based integration and short-lived branches, build-once/promote-the-same-artifact discipline, hermetic and reproducible builds, dependency and layer caching for fast feedback, the test pyramid mapped onto pipeline stages, required status checks and branch protection, quality and security gates (lint, type-check, SAST, dependency/SCA scanning, license checks) as blocking vs advisory, artifact and container registries with immutable versioning and provenance, environment promotion (build → test → stage → prod), deployment strategies the pipeline triggers (blue-green, canary, rolling, feature-flag-gated), pipeline secrets and least-privilege CI credentials (OIDC over long-lived tokens), DORA delivery metrics (deployment frequency, lead time, change-failure rate, MTTR), flaky-test quarantine, pipeline observability, and rollback/auto-revert on failed gates. Stack-agnostic across GitHub Actions, GitLab CI, Jenkins, CircleCI, and equivalents.
jacob-balslev/skills
Stars: 2Claude CodeCodexEnforces disciplined, complete, evidence-backed execution for tasks where honesty and coverage matter more than brevity: audits, diagnostic reports, tracked-task creation from findings, acceptance-criteria verification, research briefs, and any enumerated output that later work will depend on. Teaches WHY agents fail at completeness — sycophancy, premise adoption, summary-first compression, instruction-density loss, long-horizon attention decay, self-critique echo chambers, reasoning-masked agreement, verification theater, and delegation-as-proof — and the structural countermeasures: pre-task scope declaration, count-preserving enumeration, step-level evidence receipts, externally grounded critique, provenance labels, explicit partial/completeness receipts, and runtime enforcement where available. Do NOT use for choosing the shortest task route (use `task-path-optimization`), broad artifact-quality standards (use `best-practice`), result scoring (use `evaluation`), the compact pre-output enforcement gate (use `no-cutting-corners`), or compression after complete enumeration (use `summarization`).
jacob-balslev/skills
Stars: 2Claude CodeCodexRepost external blog articles into StaticFlow with style-aware translation, adaptive source normalization, image ingestion, and verified publish updates.
zero-yx/static_flow
Stars: 0Claude CodeCodexhariom710/Moirah-AI
Stars: 0Claude CodeCodex使用 p5.js 创作带有种子随机性和交互式参数探索的算法艺术。当用户请求使用代码创作艺术、生成艺术、算法艺术、流场或粒子系统时使用此技能。创作原创算法艺术,而非复制现有艺术家的作品,以避免侵犯版权。
Fantasia1999/skills-zh
Stars: 1Claude CodeCodex当用户想要创建、读取、编辑或操作 Word 文档(.docx 文件)时,使用此技能。触发条件包括:任何提及“Word 文档”、“word document”、“.docx”的情况,或要求生成包含目录、标题、页码或信头等格式的专业文档。当从 .docx 文件中提取或重组内容、在文档中插入或替换图片、在 Word 文件中执行查找和替换、处理修订或批注,或将内容转换为精美的 Word 文档时,也应使用此技能。如果用户要求将“报告”、“备忘录”、“信函”、“模板”或类似的交付成果作为 Word 或 .docx 文件,请使用此技能。请勿用于 PDF、电子表格、Google Docs 或与文档生成无关的常规编码任务。
Fantasia1999/skills-zh
Stars: 1Claude CodeCodex当用户希望对 PDF 文件进行任何操作时,请使用此技能。这包括读取或从 PDF 中提取文本/表格、将多个 PDF 合并为一个、拆分 PDF、旋转页面、添加水印、创建新 PDF、填写 PDF 表单、加密/解密 PDF、提取图像以及对扫描的 PDF 进行 OCR 以使其可搜索。如果用户提到 .pdf 文件或要求生成一个,请使用此技能。
Fantasia1999/skills-zh
Stars: 1Claude CodeCodex一套用于使用现代前端Web技术(React、Tailwind CSS、shadcn/ui)创建精细、多组件 claude.ai HTML 工件的工具集。适用于需要状态管理、路由或 shadcn/ui 组件的复杂工件 - 不适用于简单的单文件 HTML/JSX 工件。
Fantasia1999/skills-zh
Stars: 1Claude CodeCodex用于使用 Playwright 与本地 Web 应用交互和测试的工具包。支持验证前端功能、调试 UI 行为、捕获浏览器屏幕截图以及查看浏览器日志。
Fantasia1999/skills-zh
Stars: 1Claude CodeCodex当电子表格文件是主要输入或输出时,请使用此技能。这包括用户希望:打开、读取、编辑或修复现有的 .xlsx、.xlsm、.csv 或 .tsv 文件(例如,添加列、计算公式、格式化、制图、清理混乱数据);从头开始或从其他数据源创建新电子表格;或在表格文件格式之间进行转换。特别是当用户通过名称或路径(即使是随口一提,如“我下载文件夹里的那个 xlsx”)引用电子表格文件,并希望对其进行操作或用其生成内容时,应触发此技能。同样适用于将格式不正确的表格数据文件(格式错误的行、位置不当的标题、垃圾数据)清理或重构为标准电子表格。最终交付物必须是电子表格文件。当主要交付物是 Word 文档、HTML 报告、独立的 Python 脚本、数据库管道或 Google Sheets API 集成时,即使涉及表格数据,也不要触发此技能。
Fantasia1999/skills-zh
Stars: 1Claude CodeCodexIndex and navigation skill for this repo's ROS2 family. Use when the user asks broadly about ROS2, wants an overview, asks which ROS2 skill covers a topic, or needs a starting point. For concrete ROS2 tasks such as creating nodes, defining messages, debugging QoS, writing launch files, lifecycle orchestration, TF2, diagnostics, testing, bags, or architecture, prefer the matching focused ros2-* skill.
elliewlh2094/codex-robotics-skills
Stars: 0Claude CodeCodexCRUCIBLE is an 8-agent code production pipeline built on Loop Engineering principles. It takes any coding task through Architect → Coder → Reviewer → Tester → Optimizer → Security Auditor → Documenter → Deployer before delivering production-ready, tested, optimized, secured, documented, and shippable code. A Loop Sentinel governs all feedback cycles with stagnation detection, progress thresholds, and a global step budget — the pipeline always converges or halts with a clear reason. Use CRUCIBLE for any task where quality, correctness, and production-readiness matter. Trigger whenever the user says: "build", "write", "code", "implement", "create a function / class / module / app / script / API / service", "refactor this", "I need code that does X", or invokes /crucible. Always prefer CRUCIBLE over a single-pass response when the task is non-trivial — more than ~30 lines, any business logic, any external integration. Also trigger on: "do this properly", "production-ready", "I want this reviewed", "build this right", or "make this shippable".
ismailrhassan1991-maker/crucible-
Stars: 1Claude CodeCodexSolana RedPill TEE verifier development and operations for the `web/solana-redpill-verifier` stack. Use for Pinocchio SVM proof storage, TeeProofV2 PDA layout, StoreProofV2 transactions, RedPill/TDX and NVIDIA NRAS attestation anchoring, CLAWD TEE Gateway setup, OpenAI-compatible attested inference proxying, Solana Attestation Service Token-2022 credentials, TypeScript client integration, OP-TEE signer integration, deployment, and debugging proof anchoring on Solana.
Solizardking/clawd-bot
Stars: 0Claude CodeCodex国资公司投资项目合规自查。基于地方国资监管文件(市管国有企业投资监督管理办法 + 投资事项负面清单),对投资项目进行形式要件型合规初审:金额阈值判定、报告档级识别、14项负面清单核查、关联交易排查、决策程序齐备性、量化指标计算、高压线一票否决判定、八阶段时序错位防错。当用户提到"投资合规自查""项目合规""负面清单""F8/F10""报告程序""董事会程序""三级子公司股权投资""关联交易核查""1000万/3000万阈值""当前阶段"等关键词时触发。
jarodong/soe-investment-compliance-skill
Stars: 0Claude CodeCodexbaneeishaque/ljt-520_openclaw-backup
Stars: 0Claude CodeCodexCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
kumbajirajkumar123/frontend-design
Stars: 2Claude CodeCodexUse when you have a written implementation plan to execute in a separate session with review checkpoints
Parsa-29/loop-config
Stars: 1Claude CodeCodexFind deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
Parsa-29/loop-config
Stars: 1Claude CodeCodexPlan a feature or bug fix and break it into well-formed, non-mixing Linear tasks — one parent issue per feature with ordered, dependency-linked sub-issues, each with a detailed plan, acceptance criteria, labels, and a branch name — ready for a coding agent to execute. Use when the user runs /plantask, or asks to plan and create Linear issues/tasks for a feature, bug, or piece of work.
Parsa-29/loop-config
Stars: 1Claude CodeCodexDiagnose documentation issues and generate AI-ready fix prompts
KamiJeong/tech-bridge-book
Stars: 0Claude CodeCodexDiagnose documentation issues and generate AI-ready fix prompts
KamiJeong/tech-bridge-book
Stars: 0Claude CodeCodexCalculate CDD maturity score with multi-signal quality breakdown
KamiJeong/tech-bridge-book
Stars: 0Claude CodeCodexDiagnose documentation issues and generate AI-ready fix prompts
KamiJeong/tech-bridge-book
Stars: 0Claude CodeCodexDiagnose documentation issues and generate AI-ready fix prompts
KamiJeong/tech-bridge-book
Stars: 0Claude CodeCodexCalculate CDD maturity score with multi-signal quality breakdown
KamiJeong/tech-bridge-book
Stars: 0Claude CodeCodexArquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
FISCFED9/CLI
Stars: 1Claude CodeCodex