Before your first Opsy content task, check three things separately: the Skill is available in your agent host, the correct customer project is open, and the intended Shopify store has been verified for the requested operation. Passing one check does not prove the other two. Begin with a read-only project check so you can resolve missing inputs before preparing a store change.
This guide follows the Opsy repository checked on September 23, 2026. It explains the documented setup path; it is not evidence that your computer or account has passed an installation or OAuth test. Use the current repository instructions when a command or supported tool version changes.
What do you need before installation?
Obtain both the Skill package and your customer project. The Skill contains the reusable instructions and helpers. The project contains your business context and working materials. A provider may deliver the project as a ZIP with its configuration already prepared; extract it to a stable location where your agent host can open it.
Item |
What to check |
Why it matters |
|---|---|---|
Opsy source or release |
The version or commit you intend to install |
Source files and the installed copy may differ |
Supported host |
Codex or WorkBuddy, as described by the repository |
The host must recognize the Skill |
Runtime prerequisites |
The current repository's Node, Git and CLI requirements |
Installing the Skill does not install all dependencies |
Customer project |
Its project marker, business materials and owner |
The agent needs the correct working context |
Store identity |
The intended permanent Shopify domain |
A successful connection to a different store is still wrong |
How do you review the installation plan?
The repository provides installers with a dry-run option. On Windows, when installing specifically for Codex, run these from the Opsy repository root in the order shown:
.\install.ps1 -Host Codex -DryRun
.\install.ps1 -Host CodexThe first command previews the plan. The second performs the installer workflow and can change the installed Skill after its confirmation step. Choose the host you actually use. Do not copy an installation path from another person's computer or use a force-update option merely because a task has failed.
These commands install Opsy, not Node.js, Git or Shopify CLI, and they do not automatically authorize a store. If a prerequisite is missing, resolve the named prerequisite using its current installation guidance. After installation or an update, reload the Skill in the host before checking the customer project.
What should the first request say?
Open the customer project in your supported host, then ask:
Use $opsy to check this customer project before we create content. Identify the workspace, confirm the intended store, and report which tasks are available. Separate missing environment requirements, missing business information and missing permissions. Start with inspection and show the next step.
Read the result as a set of checks, not a single green light. A local status command can inspect configuration but cannot prove that the current store authorization is valid. A live read must establish the store identity and relevant granted permissions. When login or consent is needed, complete the actual Shopify browser flow; never paste a token into the chat.
When can you start a product or blog task?
Content work also needs a confirmed business model, audience, language, inquiry goal and writing voice. A store connection does not supply those business decisions. If the profile has gaps, answer the actual questions in plain language and ask Opsy to show the resulting summary for review.
For a first exercise, use one already-understood product and request a content proposal with a gap list. Keep installation, content preparation, draft creation and publication visible as separate steps. Permissions make an operation possible; the specific task still determines what should be changed.
If Opsy cannot continue, retain the exact error category and the result of the last check. An unsupported command suggests a version or path issue. Missing business information calls for a profile update. An authorization failure calls for connection verification. Reinstalling everything is not a useful default response to all three.
The Opsy installation and first-use documentation is the reference for current installer behavior. For help preparing a customer project alongside the Skill, see GRC's services and Discuss your project, including your host, the task you want to try and the specific check that remains incomplete.
Use the contact page if you prefer to describe the task and available materials in a form.
