marketing-strategy Eval
=======================

Status: failed
Score: 63/100
Risk: high
Decision: do_not_auto_install
Policy: block
Reason: Permission surface: shell or command execution, filesystem or document access

Install:
npx skills add LeadMagic/gtm-skills --skill marketing-strategy

Required checks:
- PASS Task fit: Task wording matches this skill metadata.
- PASS Install path: Install handoff is available.
- PASS Install command safety: standard package or runtime install path
- WARN Trust score: Potentially useful, but at least one trust signal needs human inspection.
- WARN Audit score: Needs review
- WARN Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- PASS License clarity: MIT
- FAIL Permission surface: shell or command execution, filesystem or document access

Warnings:
- Trust score: Potentially useful, but at least one trust signal needs human inspection.
- Audit score: Needs review
- Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- README/SKILL.md completeness: Public metadata needs stronger README/SKILL.md context
- High-risk permission hints: Shell or command execution
- Permission surface may require sandboxing
- Financial research output is not financial advice; require human review before any live investment decision
- The 'Authoritative Foundations' section cites Product-Led Marketing, Schwartz Awareness Levels, and Pulizzi Content Tilt, but all three are described with the same generic marketing-strategy sentence rather than actual framework-specific guidance.
- references/framework-notes.md also only lists framework names and does not explain how to apply them.
- templates/output-template.md does not provide a true copy-paste deliverable structure; its 'Core output' section simply repeats the SKILL.md output description.
- scripts/check-output.py expects sections like '## Framework Basis', '## Recommendation', '## Implementation Steps', and '## Metrics', but the provided output template uses different headings ('## Summary', '## Core output', '## Frameworks Applied', etc.), so the validator would fail on a deliverable produced from the template.
- Low GitHub adoption signal

Validation plan:
1. Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. Install in an isolated workspace or sandbox with no production secrets available.
3. Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. Compare the selected skill against at least one alternative when the eval status is review or failed.
5. Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when:
- teams that need a vendor-supported SLA
- production agents without a repository review
- Low GitHub adoption signal
- The 'Authoritative Foundations' section cites Product-Led Marketing, Schwartz Awareness Levels, and Pulizzi Content Tilt, but all three are described with the same generic marketing-strategy sentence rather than actual framework-specific guidance.
- No OpenAgentSkill engagement data yet
- High-risk permission hints: Shell or command execution
- Permission surface may require sandboxing
- Financial research output is not financial advice; require human review before any live investment decision

URLs:
- Skill: https://www.openagentskill.com/skills/leadmagic-marketing-strategy
- Audit: https://www.openagentskill.com/skills/leadmagic-marketing-strategy/audit
- JSON: https://www.openagentskill.com/api/agent/evals?slug=leadmagic-marketing-strategy