Show Skopos how your project tests, builds, generates, previews, and verifies work so coding agents do not have to guess.
Your existing workflow becomes available to agents without becoming automatic or unrestricted.Start with a conversation
Tell your agent the outcome and the safety boundary.
Skopos can help translate the request into its technical model after the intent is clear.
“Inspect this repository for working test, typecheck, build, browser, generation, and validation commands. Show me which ones could become Skopos project capabilities, what each command reads or changes, and which Tasks should require it. Do not activate anything until I review the proposal.”
A reviewed path from intent to project behavior.
- 01
Discover
Skopos finds configured commands and package scripts as local candidates.
- 02
Review
You inspect the exact command, working directory, effects, applicability, and required approval.
- 03
Activate
An approved declaration becomes a project capability only after its provider validates.
USE IT FOR
Common project uses.
- Typecheck the affected package
- Run checkout recovery tests
- Generate an API client
- Capture a browser accessibility check
The Skopos names for what you just configured.
- Capability
- Something the project knows how to do safely.
- Action
- The exact approved operation that performs it.
- Evidence
- The source-bound result produced by a successful run.
WHAT THIS CANNOT DO
A discovered command is only a proposal. It cannot run, satisfy a rule, or count as proof until the reviewed Action and its provider are active.
NEXT
Set the rules around those tools