Pre-install eval
wiki-knowledge-agent 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.
do not auto install
Trust score: Sparse or weak trust signals. Treat this as an experimental candidate.
Required gates
Checks an agent must pass before install
Task fit
94
Task wording matches this skill metadata.
- Evaluate wiki-knowledge-agent before installing it in an agent workflow
- note-taking
- RAG and knowledge workflows; Claude Code teams; builders willing to evaluate younger projects
Install path
92
Install handoff is available.
- npx skills add atukunare/wiki-knowledge-agent --skill wiki-knowledge-agent
Install command safety
92
standard package or runtime install path
- npx skills add atukunare/wiki-knowledge-agent --skill wiki-knowledge-agent
Trust score
57
Sparse or weak trust signals. Treat this as an experimental candidate.
- High review required
- 19 GitHub stars
- MIT
Audit score
67
Needs review
- Dependency or permission surface needs review
Agent safety gate
27
This skill should not be selected by an agent without explicit human security review.
- Do not auto-install. Inspect the source, dependencies, and permission surface first.
- Metadata combines secrets access with shell or command execution
License clarity
86
MIT
- MIT
Permission surface
22
secrets or environment access, shell or command execution
- Shell or command execution: high
- Network access: medium
- Filesystem access: medium
Validation plan
What the agent should do next
- 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
- 2Install in an isolated workspace or sandbox with no production secrets available.
- 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
- 4Compare the selected skill against at least one alternative when the eval status is review or failed.
- 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
- SKILL.md does not explicitly address prompt-injection risks from pasted or fetched content, even though the skill allows the LLM to classify, summarize, and optionally update config.
- High-risk permission hints: Shell or command execution, Secrets or environment access
- Dependency or permission surface needs review
Supporting checks
Trust signals behind the decision
README/SKILL.md completeness
pass86
Metadata includes enough usage and workflow context
Recent maintenance
pass88
2mo since push
Alternatives available
info55
No close alternatives were found in the current shortlist.