Project Flow Ops
Backlog triage with Muse across GitHub and Linear: classify PRs as merge, rebuild, close, or park, and keep public GitHub truth synced with the internal execution layer.
- What
- Backlog triage with Muse across GitHub and Linear: classify PRs as merge, rebuild, close, or park, and keep public GitHub truth synced with the internal execution layer.
- Cost
- Free
- Needs
- Use "Project Flow Ops" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: execution-flow operations that make Muse turn disconnected GitHub issues, PRs and Linear tasks into one flow when the problem is coordination, not coding. The operating model is explicit: GitHub is the public and community truth, Linear is the internal execution truth for active scheduled work, and not every GitHub issue needs a Linear issue. Muse reads the public surface first (issue/PR state, author, branch status, review comments, CI status, linked issues), classifies every item into merge, port/rebuild, close or park with a one-paragraph rationale, decides whether Linear is warranted (only when work is active, delegated, scheduled, cross-functional, or important enough to track), and keeps the two systems consistent by posting public resolutions back to GitHub and marking Linear accordingly. Review rules are strict: never merge from title or trust alone, use the full diff; CI red means classify and fix or block, never pretend it is merge-ready; if the real blocker is product direction, say so. Returns a fixed output format: public status, classification, Linear action, and the exact next operator action. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: classification is a recommendation, the merge decision stays yours; it assumes you actually use GitHub and Linear, otherwise half the model does not apply. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Project Flow Ops" with your Muse. Prerequisites: none to install. Pure guidance; GitHub and Linear access helps. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/project-flow-ops/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Triage the open PR backlog: [paste repo or PR list]. Classify each as merge, port/rebuild, close, or park." 3. Ask it for the fixed output format: public status, classification with rationale, Linear action, and the exact next operator action. Tip: ask "which of these need a Linear issue and which should stay GitHub-only?" Safety: a skill is plain-text instructions; it runs nothing by itself. Review classifications before acting on them.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.