Loading...
Loading...
Found 1,018 Skills
Manage Harness Artifact Registry (AR) via MCP. Configure private registries for Docker, Helm, Maven, npm, and PyPI artifacts, set up upstream proxies for caching public images, configure RBAC and cross-region replication, and define security scanning policies with CVE thresholds and license compliance checks. Use when asked to set up an artifact registry, configure Docker or Helm repositories, manage artifact security scanning, or set up replication. Do NOT use for creating connectors to external registries (use create-connector instead). Trigger phrases: artifact registry, docker registry, helm repository, artifact security, image scanning, private registry, artifact replication, CVE threshold, license compliance, SBOM.
Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
Package specification compliance for Elastic integration packages. Covers manifest structure (format_version, conditions, variables, routing rules), changelog schema and semantic version bumps, and alignment with the upstream elastic/package-spec. Use when building or reviewing manifest.yml, changelog.yml, or debugging elastic-package lint/check errors on package metadata.
EU MDR 2017/745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Annex VIII classification rules, Annex II/III technical files, Annex XIV clinical evaluation, and EUDAMED integration.
Workflow step compliance guidance with mandatory step reminders and visual progress tracking. Reminds Claude to complete all workflow steps before PR creation.
Expert guidance for developing, migrating, and maintaining Odoo modules (versions 14.0-19.0) following OCA conventions. Use when working with Odoo modules to create new modules from OCA template, migrate modules between versions using OpenUpgrade, extend core Odoo modules, ensure OCA compliance, and structure module files correctly. Includes OCA coding standards, module structure templates, OpenUpgrade migration patterns, and validation tools.
Expert knowledge of academic writing standards for peer-reviewed papers, including citation integrity, style compliance, clarity, and scientific writing best practices. Use when reviewing or editing academic manuscripts, papers, or research documentation.
Review code for Government of Canada authentication and identity management compliance. Checks OIDC implementations, session security, scope minimization, logout handling, and RBAC integration against ITSG-33 and TBS security standards.
Build a complete KPI framework for a creator marketing campaign from a business objective. This skill should be used when setting KPIs for an influencer campaign, building a measurement plan before campaign launch, mapping business objectives to creator marketing metrics, defining primary and secondary KPIs for a creator program, creating a metrics framework for an awareness or conversion campaign, setting measurement benchmarks by creator tier, building a KPI dashboard structure for influencer reporting, or defining success criteria before activating creators. For calculating ROI after a campaign ends, see campaign-roi-calculator. For setting numeric benchmark targets, see performance-benchmark-setter. For tracking creator posting compliance, see creator-posting-compliance-tracker.
Score how well a creator fits a brand's niche on a 1-10 scale with detailed written rationale. This skill should be used when evaluating creator-brand fit, scoring niche alignment, checking if an influencer matches a brand, assessing creator relevance, rating a creator's fit for a campaign, vetting a creator for niche match, deciding whether a creator is right for a brand, comparing creators by brand fit, or reviewing an influencer's profile against campaign requirements. For full creator vetting beyond niche fit (brand safety, rates, compliance), see creator-vetting-scorecard. For writing outreach to creators who pass vetting, see outreach-writer.
Proxy2.0 API 接口设计规范：RESTful URL 约定、Controller 模板、VO 设计、Swagger 文档注解、 错误码设计、响应格式。Use when: (1) Creating new Controller/API endpoints, (2) Designing VO classes (PageReqVO/SaveReqVO/RespVO), (3) Writing Swagger annotations, (4) Defining error codes, (5) Reviewing API design compliance.
Apply when scoping, reviewing, or documenting cross-cutting VTEX commerce architecture across storefront, IO, headless, marketplace, payments, or any other VTEX module. Grounds work in the Well-Architected Commerce framework—Technical Foundation (reliability, trust, integrity; security, infrastructure, compliance), Future-proof (innovation, simplicity, efficiency; scalable and adaptable solutions), and Operational Excellence (accuracy, accountability, data-driven improvement; process and customer experience). Routes implementation detail to product tracks (IO caching and paths, Master Data strategy, marketplace integrations). Use for solution design, architecture reviews, and RFP-level technical structure.