Orientação sobre experimentação de conteúdo e testes A/B, abrangendo design de experimentos, hipóteses, métricas, tamanho da amostra, fundamentos estatísticos, variantes gerenciadas por CMS e armadilhas comuns de análise.
Esta skill fornece orientação completa para configurar e executar experimentação de conteúdo e testes A/B em um CMS ou stack frontend. Ela cobre o design de experimentos, formulação de hipóteses, seleção de métricas de sucesso, cálculo de tamanho de amostra e fundamentos estatísticos para garantir resultados válidos. Também aborda práticas recomendadas para gerenciar variantes dentro de um CMS, além de alertar sobre armadilhas comuns de análise que podem levar a conclusões enganosas. Útil para desenvolvedores, gerentes de produto e profissionais de marketing que desejam otimizar conteúdo baseado em dados, a skill ajuda a planejar experimentos, interpretar resultados estatísticos e construir fluxos de trabalho de experimentação robustos.
npx skills add https://github.com/sanity-io/agent-toolkit/tree/main/skills/content-experimentation-best-practicesInstalled? Explore more Pesquisa e Análise de Dados skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
Orientação sobre experimentação de conteúdo e testes A/B, abrangendo design de experimentos, hipóteses, métricas, tamanho da amostra, fundamentos estatísticos, variantes gerenciadas por CMS e armadilhas comuns de análise. Use esta skill ao planejar experimentos, configurar variantes, escolher métricas de sucesso, interpretar resultados estatísticos ou construir fluxos de trabalho de experimentação em um CMS ou stack frontend.
This repo contains 3 individual skills — each has its own dedicated page.
Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other headless CMSes. Use this skill when designing or refactoring content types, deciding field shapes, debating reusable versus nested content, planning omnichannel content models, or reviewing whether a schema is too page-shaped or presentation-driven.
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, and the App SDK. Use this skill whenever working with Sanity schemas, defineType or defineField, GROQ or defineQuery, content modeling, Presentation or preview setups, Sanity-powered frontend integrations, Sanity Functions, documentEventHandler, defineDocumentFunction, defineMediaLibraryAssetFunction, @sanity/functions, @sanity/blueprints, sanity.blueprint.ts, event-driven content automation, or when reviewing and fixing a Sanity codebase.
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.