Preflight skill-integrity check: validate what a run actually installs

Open
#287 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
go

Research direction

Start by reading internal/skill/installer.go around post-install and run.go before case execution, then review the fault-injection context in #280 and the source validator from #281. Done requires a settled hook, scope, failure policy, and relationship to a future baseline before implementing preflight validation of the evaluated artifact.

Written by the indexing model from the issue text.

Description

Context. #280's fault-injection experiment showed that skill damage degrades evaluations silently, and #281 ships a source-level linter (skill-up validate --skill). By design that linter does not see the evaluated artifact: skills.include/skills.exclude can drop cited files after source validation passes, and nothing re-checks the skill between validate and run.

What a preflight would need (open questions, not a proposal yet):

  1. Hook point: after skill installation into the runtime workspace (internal/skill/installer.go post-install) vs. in run.go before case execution.
  2. Scope: once per skill, or per case when include/exclude differ.
  3. Failure policy: warn vs. abort; whether it follows a --strict-style opt-in or its own config.
  4. Relationship to content-level integrity: existence checks catch deletion/omission; truncation and corruption need a baseline (manifest/hash, item 3 in #280). A preflight should consume such a baseline if/when it exists.

Happy to prototype once the direction is settled.

Dominant language
Go
Stars
1.5k
Forks
134
Avg merge
1d 22h
Merged PRs (30d)
61

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from alibaba/skill-up

All issues in alibaba/skill-up

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.