Star200+

Pre-install eval

ew Eval report.

A machine-readable install decision for agents: task fit, Trust Score, Audit Score, install safety, permission surface, and a concrete validation plan before this skill touches a workspace.

Needs reviewMedium riskREVIEW Policy
70
Eval report
70
Trust
76
Audit
60
Agent safety

manual review

Require human approval before installing into a real workspace.

Required gates

Checks an agent must pass before install

Open JSON

Task fit

94

pass

Task wording matches this skill metadata.

  • Evaluate ew before installing it in an agent workflow
  • business
  • Research agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add Deupaxx/EveryDay-Writer --skill ew

Install command safety

92

pass

standard package or runtime install path

  • npx skills add Deupaxx/EveryDay-Writer --skill ew

Trust score

70

warn

Potentially useful, but at least one trust signal needs human inspection.

  • Manual review
  • 28 GitHub stars
  • MIT

Audit score

76

warn

Needs review

  • The SKILL.md excerpt is truncated; the full file must be complete and self-contained for the dispatcher to work correctly.

Agent safety gate

60

warn

Usable candidate, but the agent should surface permission and audit notes before installation.

  • Require human approval before installing into a real workspace.
  • The SKILL.md excerpt is truncated; the full file must be complete and self-contained for the dispatcher to work correctly.

License clarity

86

pass

MIT

  • MIT

Permission surface

86

pass

filesystem or document access

  • Network access: medium
  • Filesystem access: medium

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
  • Low GitHub adoption signal
  • The SKILL.md excerpt is truncated; the full file must be complete and self-contained for the dispatcher to work correctly.
  • The skill instructs reading files from the user's home directory (~/.everyday-writer/). While legitimate for voice profiles, this could be a privacy concern if the skill is used in a sandboxed environment; ensure the skill only accesses files the user has explicitly created and does not follow symlinks or read arbitrary paths.
  • The sub-skills referenced in the dispatch map are not included in the submitted directory. The skill depends on them; ensure they are present in the repository and properly documented.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

2d since push

Alternatives available

pass

82

Alternative skills are available for comparison.