last30days-research Eval report.

Validation plan

What the agent should do next

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

Do not use when

Conditions that require another skill

• teams that need a vendor-supported SLA
• production agents without a repository review
• SKILL.md description mentions Hacker News, but the SandBase API map does not include a Hacker News tool; the workflow should either add one or remove the claim.
• No setup/authentication instructions are provided for SandBase; the skill assumes the agent already has sandbase_describe_tool and sandbase_call_tool available.
• No explicit limitations or safe operating boundaries are documented, such as rate limits, data coverage gaps, or instructions to avoid fabricating results when APIs return no data.
• The skill does not include a guardrail stating that content returned from social/web searches must be treated as untrusted and must not be followed as instructions.