AgentStack
SKILL verified MIT Self-run

Control Preflight Reflect

skill-mr-fang-vlsi-edagent-control-preflight-reflect · by Mr-Fang-VLSI

Before each experiment, analyze latest route/STA evidence, reflect on method gaps, and output concrete improvement hypotheses and next-step A/B plan. Use when user asks to start new experiments or when model/flow conclusions may be unstable.

No reviews yet
0 installs
12 views
0.0% view→install

Install

$ agentstack add skill-mr-fang-vlsi-edagent-control-preflight-reflect

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Control Preflight Reflect? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Control Preflight Reflect

Run this skill before submitting new experiment batches.

Background Knowledge Links

This skill should stay linked to:

  1. the current route-policy and comparison-policy KB context,
  2. local paper-derived or primary-source notes when assumptions about routing behavior may drift,
  3. experiment-experience artifacts from eda-experiment-phenomenology-analyst when similar branches were already attempted,
  4. eda-context-accessor when current KB or paper context is missing from the preflight brief.

If the latest evidence contradicts background knowledge, surface that contradiction directly in the reflection artifact and trigger KB feedback rather than hiding it inside a generic root cause label.

Mandatory outputs

  1. preflight_reflection_*.md
  2. selected next-step plan (A/B/C)
  3. explicit go/no-go for new experiment submission

Operational References

  1. Load references/evidence-lock.md when collecting required artifacts and deciding whether the run is in insufficient_evidence state.
  2. Load references/checklist.md when scoring the explicit preflight checks and producing pass or fail per item.
  3. Load references/reflection-artifact.md when writing the root-cause ranking, A/B/C plan, and acceptance criteria.
  4. Load references/model-gap-patterns.md when deciding whether simple min(front,back) logic should be vetoed in favor of a judgment model path.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.