Star200+

Pre-install eval

setting-up-a-project 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
72
Trust
77
Audit
61
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

84

pass

Task wording matches this skill metadata.

  • Evaluate setting-up-a-project before installing it in an agent workflow
  • research
  • Research agents workflows; Claude Code teams; builders willing to evaluate younger projects

Install path

92

pass

Install handoff is available.

  • npx skills add JetBrains/thinkrail --skill setting-up-a-project

Install command safety

92

pass

standard package or runtime install path

  • npx skills add JetBrains/thinkrail --skill setting-up-a-project

Trust score

72

warn

Good trust signals with a few areas worth checking before rollout.

  • Strong shortlist
  • 38 GitHub stars
  • Apache-2.0

Audit score

77

warn

Needs review

  • The skill references spec tools (spec_grep, spec_graph) and other skills (starting-a-new-project, importing-a-codebase, brainstorming) without providing details on how to invoke them or their availability. This may cause confusion if the environment lacks these tools.

Agent safety gate

61

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 references spec tools (spec_grep, spec_graph) and other skills (starting-a-new-project, importing-a-codebase, brainstorming) without providing details on how to invoke them or their availability. This may cause confusion if the environment lacks these tools.

License clarity

86

pass

Apache-2.0

  • Apache-2.0

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 references spec tools (spec_grep, spec_graph) and other skills (starting-a-new-project, importing-a-codebase, brainstorming) without providing details on how to invoke them or their availability. This may cause confusion if the environment lacks these tools.
  • No OpenAgentSkill engagement data yet
  • The detection step is underspecified: it does not explain how to identify a spec graph or distinguish 'real source code' from scaffolding beyond examples.

Supporting checks

Trust signals behind the decision

README/SKILL.md completeness

pass

86

Metadata includes enough usage and workflow context

Recent maintenance

pass

100

Pushed today

Alternatives available

pass

82

Alternative skills are available for comparison.