refactor(skills): draft ReadMe workflow-focused skill skeletons

[xavierandueza]

🚥 Resolves N/A — no linked ticket

🧰 Changes

• Replace onboarding/server-centric guidance with skeleton workflows for project setup, page editing, navigation, styling, and authentication recovery.
• Ground workflows in ReadMe operations and maintained product documentation, with explicit project/branch targeting and opt-in bidirectional Git sync.
• Keep authentication recovery failure-triggered and connection instructions specific to each client and surface.
• Mark unresolved functionality, documentation, and verification gaps with NEEDS_INPUT; defer a standalone endpoint-creation skill.
• Keep this draft as a staging point for follow-up contributions, not release-ready instructions.

🧬 QA & Testing

• Passed skill synchronization, frontmatter/size validation, local-reference checks, and whitespace checks.
• Before release, resolve NEEDS_INPUT gaps and validate operation contracts, page rendering, migration/setup behavior, and client-specific connection flows.
• Review workflow triggering, branch selection, full-body edits, and explicit Git-sync handling against supported ReadMe projects.

[RECORDING/IMAGES]

[greptile-apps]

Confidence Score: 3/5

[Low risk] Documentation and skill reference reorganization.

The PR is not ready to merge while standalone project questions lack a skill trigger and first-time setup writes before connecting.

Findings

1.  Project questions lose routing ▶
2.  Seeding starts before connection ▶

_{Reviews (1) · Last reviewed commit: "docs: describe staged skill workflows an..."}

[greptile-apps]

Project questions lose routing

When a user asks for their project's endpoints, page views, or search terms, none of the remaining skill descriptions matches the request. The removed mcp-server skill covered those questions, but its replacement, PROJECT-WORKFLOW.md, loads only through another workflow. The agent can miss the guidance for choosing the customer's API or the metrics API. Keep a skill trigger for these requests.

Knowledge Base Used: Agent skill catalog

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Seeding starts before connection

For a first-time Claude or Codex user, setup-project tells the agent to seed project content in step 4 but does not set up the connection until step 5. Those plugins start without a key, so the first project write cannot complete in that order. Set up the connection before seeding.