agentsclimarketplace

Review & quality

19,040 rows, by stacks then stars

1,766 of these skill files have been read, by 1,273 distinct authors, and what they tell an agent counted. What Review & quality authors agree on, and what they forbid

  • Performance review calibration desk

    MadewellRD/skills-lab/dist/vendor/google/people-talent-command-desk/performance-review-calibration-desk Skill

    2★ repo

    run a performance cycle and its calibration, covering cycle design with the rating scheme's stated meaning at each point, the population and its exclusion rules, rating proposals with the evidence behind each split between observed work and impression, write-up quality including conclusions that carry no example, calibration inputs and the session record with every movement and the reason recorded at the time, distribution before and after with guidance identified as guidance or constraint, manager-to-manager consistency, unresolved ratings kept open, and the communication package. use for review cycles, rating proposals, calibration sessions, write-up review, distribution questions, rater variance, and performance documentation gaps.

  • Talent review succession desk

    MadewellRD/skills-lab/dist/vendor/google/people-talent-command-desk/talent-review-succession-desk Skill

    2★ repo

    build critical role lists justified by consequence rather than seniority, succession benches with ready now, ready later, and no successor stated plainly, key person risk and single points of failure, development plans carrying a named gap, an owner, and a date, potential assessments with the criteria applied and their subjectivity stated, and the handling rules for a document written about people who have not been told. use for talent reviews, nine-box and potential calibration, succession planning, bench strength and internal fill readiness, emergency cover, retention risk on critical roles, and internal mobility blockers.

  • Privacy by design desk

    MadewellRD/skills-lab/dist/vendor/google/privacy-data-protection-command-desk/privacy-by-design-desk Skill

    2★ repo

    review features and changes before release, write privacy requirements as acceptance criteria an engineer can implement and a reviewer can check, assess default settings as configured rather than as available, review deceptive patterns in consent, sharing, and deletion flows, run the threshold screen that escalates a change into a full assessment, and set a gate state of cleared, cleared with conditions, or blocked. use for privacy review of a feature or release, data protection by design and by default, privacy requirements for engineering, default settings review, dark pattern review, and privacy release gating.

  • Retention deletion desk

    MadewellRD/skills-lab/dist/vendor/google/privacy-data-protection-command-desk/retention-deletion-desk Skill

    2★ repo

    build the retention schedule with a period trigger event and statutory citation or documented rationale per record class, run the legal hold check before any disposal, set the disposal method per system including backups archives exports and vendor-held copies, and record deletion verification from the system rather than from a closed ticket. use for retention schedules and record classes, defensible disposal, legal hold and spoliation risk, crypto-shredding and anonymization, backup expiry cycles, ttl implementation, over-retention findings, and data held past its own period.

  • Security privacy review desk

    MadewellRD/skills-lab/dist/vendor/google/procurement-vendor-management-command-desk/security-privacy-review-desk Skill

    2★ repo

    coordinate supplier security and privacy reviews by checking whether an attestation report actually covers the service being bought for a period that has not expired, reading the exceptions and qualifications rather than the cover page, treating questionnaire answers as assertions to be corroborated, establishing the processing role data protection terms subprocessors and transfer mechanism, and tracking findings and approval conditions that each carry a named owner and a due date. use for vendor security reviews, third party attestation and audit report analysis, security questionnaires, penetration test evidence, dpa and subprocessor review, cross border transfer mechanisms, and conditional approval tracking.

  • Supplier integrity screening desk

    MadewellRD/skills-lab/dist/vendor/google/procurement-vendor-management-command-desk/supplier-integrity-screening-desk Skill

    2★ repo

    verify the legal contracting entity and its ownership chain, run sanctions denied party and debarment screening with the provider and date recorded, review conflicts of interest and anti-bribery exposure through intermediaries, test financial viability against the length of the commitment, check certificates of insurance for coverage type limit expiry and named insured, and establish supply chain labor and sustainability obligations. use for supplier due diligence, entity and beneficial ownership verification, sanctions and exclusion screening, conflict of interest declarations, third party anti-corruption assessment, vendor financial health checks, and insurance certificate validation.

  • Deal review desk

    MadewellRD/skills-lab/dist/vendor/google/sales-command-desk/deal-review-desk Skill

    2★ repo

    prepare internal deal reviews with risks, asks, commercial impact, approvals, and recommended decisions. use when Gemini needs to perform or continue sales revenue command desk work involving accounts, leads, opportunities, crm, calendar, email, files, prospecting, proposals, forecasts, renewals, or customer handoffs.

  • Implementation handoff desk

    MadewellRD/skills-lab/dist/vendor/google/sdlc-command-desk/implementation-handoff-desk Skill

    2★ repo

    create, review, refine, and package connector-grounded implementation handoffs for coding agents after requirements, discovery, architecture, and issue planning are complete. use when the user asks for Jules instructions, branch work, commit plans, pull request handoffs, halt-resume prompts, merge-train runbooks, repo cleanup prompts, docs/proof handoffs, or low-token coding-agent execution plans backed by github, issues, docs, ci checks, and source facts.

  • Review quality desk

    MadewellRD/skills-lab/dist/vendor/google/sdlc-command-desk/review-quality-desk Skill

    2★ repo

    create connector-grounded pull request review, diff risk, quality gate, missing-test, scope creep, and approve/comment/request-changes recommendations from github prs, changed files, checks, tests, code ownership, issues, and review comments. use when Gemini needs to review a pr, assess implementation quality, identify regressions, draft review comments, summarize risk, verify acceptance criteria, or prepare review handoff notes for implementation-handoff-desk.

  • Verification desk

    MadewellRD/skills-lab/dist/vendor/google/sdlc-command-desk/verification-desk Skill

    2★ repo

    create connector-grounded verification and validation artifacts for software delivery. use when Gemini needs to prove implemented work satisfies requirements, build requirements traceability matrices, assess acceptance gates, validate test and ci evidence, identify release blockers, or prepare downstream handoff notes for release, docs, review, or implementation-handoff-desk workflows.

  • Application security review desk

    MadewellRD/skills-lab/dist/vendor/google/security-command-desk/application-security-review-desk Skill

    2★ repo

    perform secure code review and analysis triage on application source, covering injection deserialization ssrf path traversal and template injection, cross-site scripting and request forgery, insecure direct object reference and mass assignment, unsafe file handling and upload paths, cryptographic primitive misuse, race conditions, sensitive data in logs and errors, static and dynamic analysis triage with dispositioned false positives, coverage against the applicable verification standard, and code-level remediation with the test that proves the fix. use for security code review of a diff or service, scanner triage, vulnerability class assessment, and remediation guidance.

  • Security architecture review desk

    MadewellRD/skills-lab/dist/vendor/google/security-command-desk/security-architecture-review-desk Skill

    2★ repo

    review a system or change design for security control placement, covering trust boundary mapping, data flow analysis, conformance to the reference architecture, deviations and compensating controls, fail-open and fail-closed behavior, blast radius, conditions of approval, and residual design risk with the accepting party named. use for design reviews, architecture review board submissions, new service or major change assessment, segmentation and boundary decisions, and security sign-off before build starts.

  • Vendor security review desk

    MadewellRD/skills-lab/dist/vendor/google/security-command-desk/vendor-security-review-desk Skill

    2★ repo

    run third-party security review across vendor tiering and inherent risk rating by data shared and integration depth, attestation and certification review bounded to the stated scope period and exceptions, questionnaire gap analysis against evidence, required contractual and technical controls, integration and access review of tokens keys and subprocessors, continuous monitoring by tier, and offboarding with access revocation and data deletion. use for vendor security assessment, saas onboarding, attestation review, subprocessor risk, and third-party offboarding.

  • Backup restore desk

    MadewellRD/skills-lab/dist/vendor/google/sre-reliability-command-desk/backup-restore-desk Skill

    2★ repo

    check backup coverage against the data inventory, record mechanism schedule retention and immutability with their sources, write the restore procedure and its measured time from a dated drill, verify integrity and deletion resistance including ransomware and accidental deletion, and name every dataset that has never had a restore proven. use for backup coverage, retention and immutability review, restore drills, point-in-time recovery, and data loss risk assessment.

  • Production readiness review desk

    MadewellRD/skills-lab/dist/vendor/google/sre-reliability-command-desk/production-readiness-review-desk Skill

    2★ repo

    run a production readiness review or support acceptance review with a gate set scored pass, waived, failed, or not assessed against named evidence, a launch or acceptance decision with conditions, waivers carrying a named owner and an expiry date, hand-back criteria, and the reliability debt the service enters production carrying.

  • Reliability review desk

    MadewellRD/skills-lab/dist/vendor/google/sre-reliability-command-desk/reliability-review-desk Skill

    2★ repo

    run the recurring service reliability review covering error budget attainment and burn across the period, error budget policy adjudication including whether a freeze applies and its exception path, incident page and toil trends, open postmortem actions and expiring waivers, the reliability risk register with exposure and owner, objective revision proposals, and a roadmap that ranks reliability debt by journey impact rather than by the loudest incident.

  • Ai safety review desk

    MadewellRD/skills-lab/dist/vendor/openai/ai-engineering-command-desk/ai-safety-review-desk Skill

    2★ repo

    review AI capability risks including misuse, policy compliance, privacy, security, hallucination harm, data leakage, autonomy, tool-use risk, user impact, and mitigations.

  • Quality assurance review desk

    MadewellRD/skills-lab/dist/vendor/openai/customer-support-command-desk/quality-assurance-review-desk Skill

    2★ repo

    review support interaction quality against a scorecard with every score tied to quoted ticket evidence, a sampling plan stating the population, the selection method, and what the sample size can actually support, calibration sessions with reviewer variance reported, findings separated into agent behavior, missing knowledge, broken process, and product cause, coaching actions with follow-up dates, appeals, and the honest limits of automated scoring. use for qa programs, ticket audits, calibration, and coaching planning.

  • Month end close desk

    MadewellRD/skills-lab/dist/vendor/openai/finance-accounting-command-desk/month-end-close-desk Skill

    2★ repo

    run the close calendar and name the dependency holding up anything late, test cutoff at the period boundary, assemble the journal entry package with a preparer and a separate reviewer on every entry, establish accrual completeness from what was received rather than what was invoiced, manage reversing entries, agree intercompany positions before elimination, and run the flux review against the reconciled trial balance. use for month end and quarter end close, close blockers, adjusting entries, accruals, cutoff testing, and flux analysis.

  • Engineering cost review desk

    MadewellRD/skills-lab/dist/vendor/openai/finops-command-desk/engineering-cost-review-desk Skill

    2★ repo

    run team-facing cloud cost reviews presenting spend in the vocabulary of the services a team actually owns, decomposing movement into consumption rate and allocation change, converting findings into an action set with named owners and dates, placing cost signals where engineering decisions already happen, and proposing guardrails split into what should block provisioning and what should only inform. use for team cost reviews, engineering scorecards, cost accountability models, and guardrail design.

  • Compensation review cycle desk

    MadewellRD/skills-lab/dist/vendor/openai/people-talent-command-desk/compensation-review-cycle-desk Skill

    2★ repo

    run a merit cycle against the approved budget pool with what the pool is a percentage of, refresh salary bands and name who falls below range as a result, price roles from market survey data carrying its survey, cut, effective date, and aging factor, apply the merit model with performance, compa-ratio, and tenure entering it explicitly, surface compression and inversion against the people it affects, run pay equity cohorts with their controls and the gap those controls do not explain, and resolve pay transparency obligations per jurisdiction. use for merit and focal cycles, band and structure refresh, market pricing, compa-ratio and range penetration reads, promotion and off-cycle funding, retention and counteroffer analysis, and pay equity remediation.

  • Performance review calibration desk

    MadewellRD/skills-lab/dist/vendor/openai/people-talent-command-desk/performance-review-calibration-desk Skill

    2★ repo

    run a performance cycle and its calibration, covering cycle design with the rating scheme's stated meaning at each point, the population and its exclusion rules, rating proposals with the evidence behind each split between observed work and impression, write-up quality including conclusions that carry no example, calibration inputs and the session record with every movement and the reason recorded at the time, distribution before and after with guidance identified as guidance or constraint, manager-to-manager consistency, unresolved ratings kept open, and the communication package. use for review cycles, rating proposals, calibration sessions, write-up review, distribution questions, rater variance, and performance documentation gaps.

  • Talent review succession desk

    MadewellRD/skills-lab/dist/vendor/openai/people-talent-command-desk/talent-review-succession-desk Skill

    2★ repo

    build critical role lists justified by consequence rather than seniority, succession benches with ready now, ready later, and no successor stated plainly, key person risk and single points of failure, development plans carrying a named gap, an owner, and a date, potential assessments with the criteria applied and their subjectivity stated, and the handling rules for a document written about people who have not been told. use for talent reviews, nine-box and potential calibration, succession planning, bench strength and internal fill readiness, emergency cover, retention risk on critical roles, and internal mobility blockers.

  • Privacy by design desk

    MadewellRD/skills-lab/dist/vendor/openai/privacy-data-protection-command-desk/privacy-by-design-desk Skill

    2★ repo

    review features and changes before release, write privacy requirements as acceptance criteria an engineer can implement and a reviewer can check, assess default settings as configured rather than as available, review deceptive patterns in consent, sharing, and deletion flows, run the threshold screen that escalates a change into a full assessment, and set a gate state of cleared, cleared with conditions, or blocked. use for privacy review of a feature or release, data protection by design and by default, privacy requirements for engineering, default settings review, dark pattern review, and privacy release gating.

  • Retention deletion desk

    MadewellRD/skills-lab/dist/vendor/openai/privacy-data-protection-command-desk/retention-deletion-desk Skill

    2★ repo

    build the retention schedule with a period trigger event and statutory citation or documented rationale per record class, run the legal hold check before any disposal, set the disposal method per system including backups archives exports and vendor-held copies, and record deletion verification from the system rather than from a closed ticket. use for retention schedules and record classes, defensible disposal, legal hold and spoliation risk, crypto-shredding and anonymization, backup expiry cycles, ttl implementation, over-retention findings, and data held past its own period.

  • Security privacy review desk

    MadewellRD/skills-lab/dist/vendor/openai/procurement-vendor-management-command-desk/security-privacy-review-desk Skill

    2★ repo

    coordinate supplier security and privacy reviews by checking whether an attestation report actually covers the service being bought for a period that has not expired, reading the exceptions and qualifications rather than the cover page, treating questionnaire answers as assertions to be corroborated, establishing the processing role data protection terms subprocessors and transfer mechanism, and tracking findings and approval conditions that each carry a named owner and a due date. use for vendor security reviews, third party attestation and audit report analysis, security questionnaires, penetration test evidence, dpa and subprocessor review, cross border transfer mechanisms, and conditional approval tracking.

  • Supplier integrity screening desk

    MadewellRD/skills-lab/dist/vendor/openai/procurement-vendor-management-command-desk/supplier-integrity-screening-desk Skill

    2★ repo

    verify the legal contracting entity and its ownership chain, run sanctions denied party and debarment screening with the provider and date recorded, review conflicts of interest and anti-bribery exposure through intermediaries, test financial viability against the length of the commitment, check certificates of insurance for coverage type limit expiry and named insured, and establish supply chain labor and sustainability obligations. use for supplier due diligence, entity and beneficial ownership verification, sanctions and exclusion screening, conflict of interest declarations, third party anti-corruption assessment, vendor financial health checks, and insurance certificate validation.

  • Deal review desk

    MadewellRD/skills-lab/dist/vendor/openai/sales-command-desk/deal-review-desk Skill

    2★ repo

    prepare internal deal reviews with risks, asks, commercial impact, approvals, and recommended decisions. use when ChatGPT needs to perform or continue sales revenue command desk work involving accounts, leads, opportunities, crm, calendar, email, files, prospecting, proposals, forecasts, renewals, or customer handoffs.

  • Implementation handoff desk

    MadewellRD/skills-lab/dist/vendor/openai/sdlc-command-desk/implementation-handoff-desk Skill

    2★ repo

    create, review, refine, and package connector-grounded implementation handoffs for coding agents after requirements, discovery, architecture, and issue planning are complete. use when the user asks for Codex instructions, branch work, commit plans, pull request handoffs, halt-resume prompts, merge-train runbooks, repo cleanup prompts, docs/proof handoffs, or low-token coding-agent execution plans backed by github, issues, docs, ci checks, and source facts.

  • Review quality desk

    MadewellRD/skills-lab/dist/vendor/openai/sdlc-command-desk/review-quality-desk Skill

    2★ repo

    create connector-grounded pull request review, diff risk, quality gate, missing-test, scope creep, and approve/comment/request-changes recommendations from github prs, changed files, checks, tests, code ownership, issues, and review comments. use when ChatGPT needs to review a pr, assess implementation quality, identify regressions, draft review comments, summarize risk, verify acceptance criteria, or prepare review handoff notes for implementation-handoff-desk.

  • Verification desk

    MadewellRD/skills-lab/dist/vendor/openai/sdlc-command-desk/verification-desk Skill

    2★ repo

    create connector-grounded verification and validation artifacts for software delivery. use when ChatGPT needs to prove implemented work satisfies requirements, build requirements traceability matrices, assess acceptance gates, validate test and ci evidence, identify release blockers, or prepare downstream handoff notes for release, docs, review, or implementation-handoff-desk workflows.

  • Application security review desk

    MadewellRD/skills-lab/dist/vendor/openai/security-command-desk/application-security-review-desk Skill

    2★ repo

    perform secure code review and analysis triage on application source, covering injection deserialization ssrf path traversal and template injection, cross-site scripting and request forgery, insecure direct object reference and mass assignment, unsafe file handling and upload paths, cryptographic primitive misuse, race conditions, sensitive data in logs and errors, static and dynamic analysis triage with dispositioned false positives, coverage against the applicable verification standard, and code-level remediation with the test that proves the fix. use for security code review of a diff or service, scanner triage, vulnerability class assessment, and remediation guidance.

  • Security architecture review desk

    MadewellRD/skills-lab/dist/vendor/openai/security-command-desk/security-architecture-review-desk Skill

    2★ repo

    review a system or change design for security control placement, covering trust boundary mapping, data flow analysis, conformance to the reference architecture, deviations and compensating controls, fail-open and fail-closed behavior, blast radius, conditions of approval, and residual design risk with the accepting party named. use for design reviews, architecture review board submissions, new service or major change assessment, segmentation and boundary decisions, and security sign-off before build starts.

  • Vendor security review desk

    MadewellRD/skills-lab/dist/vendor/openai/security-command-desk/vendor-security-review-desk Skill

    2★ repo

    run third-party security review across vendor tiering and inherent risk rating by data shared and integration depth, attestation and certification review bounded to the stated scope period and exceptions, questionnaire gap analysis against evidence, required contractual and technical controls, integration and access review of tokens keys and subprocessors, continuous monitoring by tier, and offboarding with access revocation and data deletion. use for vendor security assessment, saas onboarding, attestation review, subprocessor risk, and third-party offboarding.

  • Backup restore desk

    MadewellRD/skills-lab/dist/vendor/openai/sre-reliability-command-desk/backup-restore-desk Skill

    2★ repo

    check backup coverage against the data inventory, record mechanism schedule retention and immutability with their sources, write the restore procedure and its measured time from a dated drill, verify integrity and deletion resistance including ransomware and accidental deletion, and name every dataset that has never had a restore proven. use for backup coverage, retention and immutability review, restore drills, point-in-time recovery, and data loss risk assessment.

  • Production readiness review desk

    MadewellRD/skills-lab/dist/vendor/openai/sre-reliability-command-desk/production-readiness-review-desk Skill

    2★ repo

    run a production readiness review or support acceptance review with a gate set scored pass, waived, failed, or not assessed against named evidence, a launch or acceptance decision with conditions, waivers carrying a named owner and an expiry date, hand-back criteria, and the reliability debt the service enters production carrying.

  • Reliability review desk

    MadewellRD/skills-lab/dist/vendor/openai/sre-reliability-command-desk/reliability-review-desk Skill

    2★ repo

    run the recurring service reliability review covering error budget attainment and burn across the period, error budget policy adjudication including whether a freeze applies and its exception path, incident page and toil trends, open postmortem actions and expiring waivers, the reliability risk register with exposure and owner, objective revision proposals, and a roadmap that ranks reliability debt by journey impact rather than by the loudest incident.

  • Differential review

    Fodhol/skills/plugins/differential-review/skills/differential-review Skill

    2★ repo

    Performs security-focused differential review of code changes (PRs, commits, diffs). Adapts analysis depth to codebase size, uses git history for context, calculates blast radius, checks test coverage, and generates comprehensive markdown reports. Automatically detects and prevents security regressions.

    The same file is in 4 other repositories

  • Fix review

    Fodhol/skills/plugins/fix-review/skills/fix-review Skill

    2★ repo

    Verifies that git commits address security audit findings without introducing bugs. This skill should be used when the user asks to "verify these commits fix the audit findings", "check if TOB-XXX was addressed", "review the fix branch", "validate remediation commits", "did these changes address the security report", "post-audit remediation review", "compare fix commits to audit report", or when reviewing commits against security audit reports.

  • Clean branches

    toRolex/rolex-skills/skills/engineering/clean-branches Skill

    1★ repo

    清理本地和远程已合并的 Git 分支。扫描所有本地分支和远程 tracking branches,标记已合并入当前分支的分支,一次性列表让用户勾选确认后删除并验证结果。使用场景包括:分支太多要清理、合并后残留、worktree 未清理、远程 stale branches。当用户提到 清理分支/删分支/整理分支/clean branches/branch cleanup/prune branches/git clean 时务必使用。对于合并后残留的发布分支、废弃的功能分支、已修复的 bugfix 分支尤其适用。

  • Code review

    toRolex/rolex-skills/skills/engineering/code-review Skill

    1★ repo

    审查自某个固定点(commit、branch、tag 或 merge-base)以来的变更,沿两个轴进行——Standards(代码是否遵循本仓库文档化的编码规范?)和 Spec(代码是否匹配原始 issue/PRD 的要求?)。两个并行 sub-agent 分别运行审查并并排报告结果。当用户想要 review branch、PR、进行中的变更,或要求"review since X"时使用。

  • Git flow conventions

    toRolex/rolex-skills/skills/engineering/git-flow-conventions Skill

    1★ repo

    Git Flow 分支管理与提交规范指南。当用户进行分支操作、合并代码、提交 PR/MR、 规划发版、修复线上 Bug、或询问 Git 协作规范时使用。覆盖完整 Git Flow 模型 (develop/feature/release/hotfix)、分支命名规范、commit message 格式、 PR 提交流程和最佳实践。触发场景包括:创建分支、合并代码、git commit、发版、 hotfix、分支命名、PR 描述、代码审查提交。

  • Grill with docs

    toRolex/rolex-skills/skills/engineering/grill-with-docs Skill

    1★ repo

    一场无情的追问,用来打磨方案或设计,同时生成文档(ADR 和词汇表)。

  • Resolving merge conflicts

    toRolex/rolex-skills/skills/engineering/resolving-merge-conflicts Skill

    1★ repo

    当你需要解决进行中的 git merge/rebase 冲突时使用。

  • Safe pull

    toRolex/rolex-skills/skills/engineering/safe-pull Skill

    1★ repo

    Safe Git pull with rebase workflow — check remote changes, stash, rebase, restore, handle conflicts, and push. Covers main/develop sync and feature branch rebase. Use when the user says "sync", "pull latest", "拉取最新", "rebase main", "同步代码", "update branch", or wants to safely pull remote changes preserving linear history.

  • Grill me

    toRolex/rolex-skills/skills/productivity/grill-me Skill

    1★ repo

    一场无情的追问,用来打磨计划或设计。

  • Pdf review

    dss-time/repo-doctor-skills/plugins/productivity-toolkit/skills/pdf-review Skill

    1★ repo

    Default to this Skill for an unqualified PDF review and for checks involving searchable text, structure, tables, page-located claims, numeric consistency, citations, scanned pages, OCR, rendering, completeness, or visual layout. Detect available capabilities and degrade within this Skill when tools are unavailable; do not modify the source PDF or claim unsupported verification. Do not use when the user explicitly requests pdf-review-basic or a lightweight, text-only check without OCR, rendering, or complex layout review. 未限定范围的通用 PDF 审查,以及涉及可搜索文字、结构、表格、页码定位、数字一致性、引用、扫描页、OCR、渲染、完整性或视觉版式的检查,默认使用本 Skill。检测可用能力,工具不可用时仍在本 Skill 内降级;不得修改原 PDF 或声称完成不受支持的验证。用户明确指定 pdf-review-basic,或明确要求不做 OCR、渲染和复杂版式检查的轻量纯文本任务时不使用本 Skill。

  • Spreadsheet data cleaning

    dss-time/repo-doctor-skills/plugins/productivity-toolkit/skills/spreadsheet-data-cleaning Skill

    1★ repo

    Profile, clean, standardize, transform, fill, or deduplicate spreadsheet or delimited data into an authorized new output with traceable rules, before/after statistics, an audit log, and validation of formulas, encoding, dimensions, and key summaries. Do not overwrite source data, guess critical values, or delete plausible records, and degrade to a cleaning plan when execution tools are unavailable. Use excel-data-quality-check-basic instead when the user requests only a read-only data-quality audit or issue report without changes or a cleaned copy. 对电子表格或分隔数据进行画像、清洗、标准化、转换、填补或去重,并在用户授权下生成新结果,提供可追踪规则、前后统计、审计日志及公式、编码、行列数和关键汇总验证。不得覆盖原始数据、猜测关键值或删除可能有效的记录;缺少执行工具时降级为清洗计划。用户只要求只读数据质量审计或问题报告,不要求修改或清洗副本时,应使用 excel-data-quality-check-basic。

  • Api contract review

    dss-time/repo-doctor-skills/plugins/repo-doctor/skills/api-contract-review Skill

    1★ repo

    Review a specific REST, GraphQL, RPC, event, SDK, or internal-module contract across server, client, schema, documentation, and tests, classifying breaking, non-breaking, and behavioral changes. Use for API contract compatibility; do not perform a general code review, generic impact analysis, or modify the interface. 审查具体 REST、GraphQL、RPC、事件、SDK 或内部模块契约在服务端、客户端、Schema、文档和测试间的一致性,并分类破坏性、非破坏性和行为变化。用于 API 契约兼容性;不替代普通代码审查或通用影响分析,也不修改接口。

  • Configuration audit

    dss-time/repo-doctor-skills/plugins/repo-doctor/skills/configuration-audit Skill

    1★ repo

    Audit configuration sources, precedence, environment overrides, defaults, required fields, types, validation, drift, obsolete settings, dangerous defaults, undocumented variables, and credential-commit risk using repository evidence. Use for configuration-specific risk; do not perform a broad health check, read or display sensitive values, connect to external environments, or modify configuration. 基于仓库证据审计配置来源、优先级、环境覆盖、默认值、必填、类型、校验、漂移、过期项、危险默认值、未文档化变量和凭证误提交风险。用于配置专项风险;不替代广泛体检,不读取或显示敏感值、不连接外部环境,也不修改配置。

  • Database migration review

    dss-time/repo-doctor-skills/plugins/repo-doctor/skills/database-migration-review Skill

    1★ repo

    Review a concrete database schema or data migration for reversibility, data safety, locking, backfill, replication, compatibility, zero-downtime rollout, validation, and rollback. Use for migration-specific risk; do not perform generic impact analysis, execute migrations, connect to production, or modify migration files. 审查具体数据库 Schema 或数据迁移的可逆性、数据安全、锁、回填、复制、兼容、零停机发布、验证和回滚。用于迁移专项风险;不替代通用影响分析,不执行迁移、不连接生产,也不修改迁移文件。

  • Dead code verification

    dss-time/repo-doctor-skills/plugins/repo-doctor/skills/dead-code-verification Skill

    1★ repo

    Verify whether a specific symbol, file, route, configuration path, or feature is safely removable by checking static and dynamic usage, registries, build entries, templates, plugins, scripts, and external contracts. Use for evidence of unused code; do not perform general impact analysis, assume absence from text search proves safety, or delete code. 通过检查静态与动态使用、注册器、构建入口、模板、插件、脚本和外部契约,验证具体符号、文件、路由、配置路径或功能是否可安全删除。用于无用代码证据;不替代通用影响分析,不把文本搜索无结果当安全证明,也不删除代码。

  • Project health check

    dss-time/repo-doctor-skills/plugins/repo-doctor/skills/project-health-check Skill

    1★ repo

    Diagnose broad repository health across architecture, correctness, security, performance, dependencies, tests, and general release risk. Use a specialized review for one bounded dependency upgrade, API contract, database migration, dead-code candidate, security surface, performance regression, or configuration scope; use release-readiness-check for a specific release gate. 从架构、正确性、安全、性能、依赖、测试和一般发布风险等方面广泛诊断项目健康度。单一依赖升级、API 契约、数据库迁移、死代码候选、安全边界、性能回归或配置范围应交给相应专项审查;具体候选版本门禁使用 release-readiness-check。

  • Release readiness check

    dss-time/repo-doctor-skills/plugins/repo-doctor/skills/release-readiness-check Skill

    1★ repo

    Perform an evidence-backed, read-only release gate for a specific candidate version and return GO, GO WITH CONDITIONS, or NO-GO after checking workspace state, versioning, changes, validation, compatibility, rollback, documentation, and sensitive artifacts. Use for release candidates; do not use as a broad project health check or execute release, commit, tag, push, or version changes. 针对具体候选版本执行有证据的只读发布门禁,检查工作区、版本、变更、验证、兼容性、回滚、文档和敏感产物后给出 GO、GO WITH CONDITIONS 或 NO-GO。用于候选版本;不作为广泛项目体检,也不执行发布、提交、tag、push 或版本修改。

  • Safe code review

    dss-time/repo-doctor-skills/plugins/repo-doctor/skills/safe-code-review Skill

    1★ repo

    Review a code change or PR broadly for correctness, compatibility, security, maintainability, and tests. Use security-focused-review, performance-regression-analysis, or api-contract-review when the user requests one bounded specialist assessment; do not implement fixes. 广泛审查代码改动或 PR 的正确性、兼容性、安全性、可维护性和测试。用户要求单一安全、性能回归或 API 契约专项时分别使用对应专项 Skill;本 Skill 不实施修复。

  • Security focused review

    dss-time/repo-doctor-skills/plugins/repo-doctor/skills/security-focused-review Skill

    1★ repo

    Perform a scoped security review by establishing assets, trust boundaries, attacker prerequisites, and evidence-backed findings across authentication, authorization, validation, injection, path handling, SSRF, XSS, CSRF, deserialization, credential handling, logging, and dependencies. Use for security depth; do not replace general code review, run attacks, access production, reveal credentials, or implement fixes. 通过建立资产、信任边界和攻击前提,对鉴权、授权、校验、注入、路径、SSRF、XSS、CSRF、反序列化、凭证、日志和依赖执行有证据的范围化安全审查。用于安全深度审查;不替代普通代码审查,不执行攻击、不访问生产、不显示密钥,也不实施修复。

  • Cc content performance review

    clever-cc-plugins/cc-content/plugins/cc-content/skills/cc-content-performance-review Skill

    1★ repo

    Use this skill to analyze how one or more published content pieces performed and generate concrete iteration variants for the next piece. Invoke when the user says "review how this post performed", "analyze content performance", "what worked in these posts", "help me iterate on this based on the numbers", or pastes performance data (impressions, engagement rate, CTR, conversions) alongside a piece and asks what to do next. Works from whatever data the owner supplies — there is no analytics API integration. Do NOT use it to evaluate whether a positioning claim, channel allocation, or campaign goal was validated — that is a strategic-level question for cc-concept-performance-review, not this skill.

  • Cc content session wrap

    clever-cc-plugins/cc-content/plugins/cc-content/skills/cc-content-session-wrap Skill

    1★ repo

    Use this skill at the end of a content creation session to review deliverables, collect feedback, detect recurring correction patterns, and create a git commit. Invoke when the user says "wrap up", "end session", "session wrap", "wrap session", "commit session work", or "close out this session".

  • Line login

    abgne/line-dev/skills/line-login Skill

    1★ repo

    Comprehensive reference for LINE Login (OAuth 2.1) — authorization code flow, PKCE, token management, ID token JWT verification, user profiles, bot linking, and login button design. This skill should be used when the user asks to "implement LINE Login", "add Log in with LINE", "set up OAuth authorization flow", "verify an ID token", "refresh an access token", "link a bot to login", "design a login button", or mentions LINE Login, OAuth 2.1, PKCE, authorization code flow, ID token JWT verification, token refresh/revocation, user profile retrieval, bot linking, SSO login, LIFF authentication, or LINE MINI App authentication. Always use this skill whenever the user mentions LINE authentication, social login with LINE, or OAuth flows involving LINE, even if they don't explicitly say "LINE Login".

    The same file is in 3 other repositories

  • Commit

    AnotherSava/claude-code-common/claude/skills/commit Skill

    1★ repo

    Reflects on the session, then analyzes changes and generates Conventional Commit messages