Informe de auditoría del skill
define-problem-statement Informe de auditoría.
Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.
Trust Score de OpenAgentSkill
Trust Score de OpenAgentSkill
The Trust Score helps an agent decide whether a skill is safe enough to shortlist before installation.
Adopción en GitHub
Info76
643 estrellas de GitHub
Actividad de stars/forks
Info71
643 estrellas y 81 forks; la actividad de issues no está disponible en los metadatos actuales
Mantenimiento reciente
Aprobado88
1 meses desde el último push
Claridad de licencia
Aprobado86
Apache-2.0
Completitud de README/SKILL.md
Aprobado86
Los metadatos incluyen suficiente contexto de uso y flujo de trabajo
Riesgo de dependencias/runtime
Aprobado90
No hay indicios importantes de riesgo de dependencias en los metadatos públicos
Disponibilidad de instalación
Aprobado92
npx skills add product-on-purpose/pm-skills --skill define-problem-statement
Seguridad del comando de instalación
Aprobado92
Ruta estándar de paquete o instalación en tiempo de ejecución
Superficie de permisos
Aprobado86
Acceso a archivos o documentos
Evidencia del repositorio
Aprobado86
https://github.com/product-on-purpose/pm-skills/tree/main/skills/define-problem-statement
Estado de revisión
Info66
Hay datos de revisión por IA disponibles
Resultados comprobados por Agent
Info54
Aún no hay datos de resultados del Agent
Comprobaciones
Revisión de instalación y adopción
Ruta de instalación
92
npx skills add product-on-purpose/pm-skills --skill define-problem-statement
Repositorio
88
https://github.com/product-on-purpose/pm-skills/tree/main/skills/define-problem-statement
Licencia
86
Apache-2.0
Mantenimiento
88
1 meses desde el último push
Revisión por IA
55
Parsed SKILL.md metadata shows empty tags and frameworks, likely because they are nested under metadata rather than top-level frontmatter; this may reduce discoverability.
Completitud de README/SKILL.md
86
Usable description available
Riesgo de dependencias
90
No hay indicios importantes de riesgo de dependencias en los metadatos públicos
Seguridad del comando de instalación
92
Ruta estándar de paquete o instalación en tiempo de ejecución
Superficie de permisos
86
Acceso a archivos o documentos
Actividad de stars/forks
71
643 estrellas y 81 forks; la actividad de issues no está disponible en los metadatos actuales
Adopción
88
643 estrellas de GitHub
Advertencias
- Parsed SKILL.md metadata shows empty tags and frameworks, likely because they are nested under metadata rather than top-level frontmatter; this may reduce discoverability.
- No critical security concerns found; the skill only produces documents and does not execute commands or access external resources.
- Quality score needs review
Método
This report combines public metadata, AI review output, repository freshness, install readiness, OpenAgentSkill events, quality scoring, trust checks, and the agent safety gate. It is not a full source-code security review.
Comparar opciones cercanas
Skills relacionados para auditar después
copywriting
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing. For the offer underneath the copy (bonuses, guarantees, value framing), see offers.
47K Estrellas · Informe de auditoría
cro
When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't converting,' 'improve conversions,' 'why isn't this page working,' 'my landing page sucks,' 'form abandonment,' 'nobody's converting,' 'low conversion rate,' or 'this page needs work.' Use this even if the user just shares a URL and asks for feedback. For signup/registration flows, see signup. For post-signup activation, see onboarding. For popups/modals, see popups.
47K Estrellas · Informe de auditoría
marketing-psychology
When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psychology to specific pages, see cro; for pricing tactics, see pricing; for copy framing, see copywriting.
54K Estrellas · Informe de auditoría