refactor(skills): draft ReadMe workflow-focused skill skeletons - #11
xavierandueza wants to merge 4 commits into
Conversation
 |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
|
(agent response) |
| **Done:** The user approves the setup scope and which account/project to create or reuse. | ||
| 3. **Provision.** Read [Creating a project](https://docs.readme.com/main/docs/creating-a-project) and discover available onboarding operations. Create the approved account/project only through supported capabilities. If unavailable, hand the user the signup link (`https://dash.readme.com/signup`) and the documented project-creation steps; resume when they return the project link. Let the user enter credentials, consent, and billing details. | ||
| **Done:** A confirmed project link and owner exist, or a specific manual handoff is recorded. | ||
| 4. **Connect and verify.** Use the existing connection first. Only when connection setup is needed, read the [client-specific connection reference](../mcp-auth/CLIENTS.md); apply non-secret configuration only with permission, and let the user supply credentials through their client's settings. Use a supported, non-mutating project read and inspect its current schema to confirm the connection reaches the intended project. Invoke [mcp-auth](../mcp-auth/SKILL.md) only when the read fails for authentication, then retry the read after recovery. If the read is unavailable or does not succeed, stop before seeding and give the user a client-specific manual next step. |
There was a problem hiding this comment.
If a user has confirmed bidirectional Git sync but no working MCP connection, setup-project stops at step 4 before it reaches the local-file path in step 5. The user cannot seed the mapped files even though that work does not need a hosted write connection. Require the connection check for hosted writes, not for confirmed local edits.
There was a problem hiding this comment.
(agent response)
Moved write-surface selection before the hosted-access gate. Explicitly confirmed bidirectional Git-sync edits to mapped local files no longer require MCP or successful authentication; hosted writes still require a successful read of the intended project. Mixed setup keeps blocked hosted-only items pending without falling back to local files. Updated the downstream helpers, client copies, and catalogs; local checks and independent static verification pass (no live integrations claimed).
Commit: c0fc720
c0fc720 to
c1fae3d
Compare
|
(agent response) This is intentional staging: this PR changes only |
|
(agent response) No product changes: this draft intentionally stages only |
1 participant
🧰 Changes
This is a skeleton that I made for the Skills that we'll want moving forward. Other PRs merge into here, and once we're ready to go we merge this.
Note - it's intentionally minimalist at the moment so that we can continue to improve on this as we merge PRs that and we test to make sure that the skills work in actual onboarding workflows that we do.
🧬 QA & Testing
N/A - staging PR that others merge into.