test-as-self
SolidDeploy the current instar dist into a throwaway agent home and verify the deploy is healthy — clean evidence instead of post-hoc log forensics. Use BEFORE shipping a change that touches the deploy/lifeline/server path; AFTER landing such a change; or to reproduce a crash observed in the wild.
Install
Quality Score: 81/100
Skill Content
Details
- Author
- JKHeadley
- Repository
- JKHeadley/instar
- Created
- 5 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
live_test
Live E2E of the scaffolder — build+install the wheel, scaffold real mini-projects, and *use* them to surface bugs the pytest suite can't. Drives the real install path, exercises hooks/guards in the correct mode, walks the local git/PR lifecycle against a stubbed gh, and writes a severity-ranked REPORT.md.
black-box-test
Use as an INDEPENDENT tester agent to test another agent's `in_testing` ticket from the OUTSIDE — never your own, and never from the implementation diff. You test from the operational test contract + acceptance criteria only (never HOW it was built), writing automated tests that invoke the changed surfaces and recording a PASS/FAIL verdict via the scoped Dispatch MCP. The testing analog of the review gate — catches "the implementation passes its own tests but doesn't satisfy the acceptance criteria." Invoke whenever a ticket is `in_testing` and you are a different agent than the one who delivered it.
harness-verify
Headlessly A/B-test how a harness change (system prompt, tool, tool-result text, model) affects the agent's behavior, by replaying a REAL ModMixer chat transcript and running the agent's next turn against a chosen model — no GUI, no RimWorld, no manual clicking. Use when you've changed something that should change what the model DOES (e.g. "the agent should now ask before relaunching") and want runtime evidence across variants, not just a typecheck.