[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JV937T74HEFS9B4KCKC7S5":3,"skill-same:01M6JV937T74HEFS9B4KCKC7S5":70},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6JV937T74HEFS9B4KCKC7S5","project-flow-ops",null,"Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FColin4k1024\u002Ftsp\u002Fskills\u002Fproject-flow-ops\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"project flow ops","flow","project","ops","when","pull requests","linking","layer","operate","across","active","backlog","use","work","coordination","execution","pr triage","pull","linear","issues","pr","2026-11-10 10:12:30",false,"---\nname: project-flow-ops\ndescription: Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.\norigin: ECC\n---\n\n# Project Flow Ops\n\nThis skill turns disconnected GitHub issues, PRs, and Linear tasks into one execution flow.\n\nUse it when the problem is coordination, not coding.\n\n## When to Use\n\n- Triage open PR or issue backlogs\n- Decide what belongs in Linear vs what should remain GitHub-only\n- Link active GitHub work to internal execution lanes\n- Classify PRs into merge, port\u002Frebuild, close, or park\n- Audit whether review comments, CI failures, or stale issues are blocking execution\n\n## Operating Model\n\n- **GitHub** is the public and community truth\n- **Linear** is the internal execution truth for active scheduled work\n- Not every GitHub issue needs a Linear issue\n- Create or update Linear only when the work is:\n  - active\n  - delegated\n  - scheduled\n  - cross-functional\n  - important enough to track internally\n\n## Core Workflow\n\n### 1. Read the public surface first\n\nGather:\n\n- GitHub issue or PR state\n- author and branch status\n- review comments\n- CI status\n- linked issues\n\n### 2. Classify the work\n\nEvery item should end up in one of these states:\n\n| State | Meaning |\n|-------|---------|\n| Merge | self-contained, policy-compliant, ready |\n| Port\u002FRebuild | useful idea, but should be manually re-landed inside ECC |\n| Close | wrong direction, stale, unsafe, or duplicated |\n| Park | potentially useful, but not scheduled now |\n\n### 3. Decide whether Linear is warranted\n\nCreate or update Linear only if:\n\n- execution is actively planned\n- multiple repos or workstreams are involved\n- the work needs internal ownership or sequencing\n- the issue is part of a larger program lane\n\nDo not mirror everything mechanically.\n\n### 4. Keep the two systems consistent\n\nWhen work is active:\n\n- GitHub issue\u002FPR should say what is happening publicly\n- Linear should track owner, priority, and execution lane internally\n\nWhen work ships or is rejected:\n\n- post the public resolution back to GitHub\n- mark the Linear task accordingly\n\n## Review Rules\n\n- Never merge from title, summary, or trust alone; use the full diff\n- External-source features should be rebuilt inside ECC when they are valuable but not self-contained\n- CI red means classify and fix or block; do not pretend it is merge-ready\n- If the real blocker is product direction, say so instead of hiding behind tooling\n\n## Output Format\n\nReturn:\n\n```text\nPUBLIC STATUS\n- issue \u002F PR state\n- CI \u002F review state\n\nCLASSIFICATION\n- merge \u002F port-rebuild \u002F close \u002F park\n- one-paragraph rationale\n\nLINEAR ACTION\n- create \u002F update \u002F no Linear item needed\n- project \u002F lane if applicable\n\nNEXT OPERATOR ACTION\n- exact next move\n```\n\n## Good Use Cases\n\n- \"Audit the open PR backlog and tell me what to merge vs rebuild\"\n- \"Map GitHub issues into our ECC 1.x and ECC 2.0 program lanes\"\n- \"Check whether this needs a Linear issue or should stay GitHub-only\"\n","# Project Flow Ops\n\nThis skill turns disconnected GitHub issues, PRs, and Linear tasks into one execution flow.\n\nUse it when the problem is coordination, not coding.\n\n## When to Use\n\n- Triage open PR or issue backlogs\n- Decide what belongs in Linear vs what should remain GitHub-only\n- Link active GitHub work to internal execution lanes\n- Classify PRs into merge, port\u002Frebuild, close, or park\n- Audit whether review comments, CI failures, or stale issues are blocking execution\n\n## Operating Model\n\n- **GitHub** is the public and community truth\n- **Linear** is the internal execution truth for active scheduled work\n- Not every GitHub issue needs a Linear issue\n- Create or update Linear only when the work is:\n  - active\n  - delegated\n  - scheduled\n  - cross-functional\n  - important enough to track internally\n\n## Core Workflow\n\n### 1. Read the public surface first\n\nGather:\n\n- GitHub issue or PR state\n- author and branch status\n- review comments\n- CI status\n- linked issues\n\n### 2. Classify the work\n\nEvery item should end up in one of these states:\n\n| State | Meaning |\n|-------|---------|\n| Merge | self-contained, policy-compliant, ready |\n| Port\u002FRebuild | useful idea, but should be manually re-landed inside ECC |\n| Close | wrong direction, stale, unsafe, or duplicated |\n| Park | potentially useful, but not scheduled now |\n\n### 3. Decide whether Linear is warranted\n\nCreate or update Linear only if:\n\n- execution is actively planned\n- multiple repos or workstreams are involved\n- the work needs internal ownership or sequencing\n- the issue is part of a larger program lane\n\nDo not mirror everything mechanically.\n\n### 4. Keep the two systems consistent\n\nWhen work is active:\n\n- GitHub issue\u002FPR should say what is happening publicly\n- Linear should track owner, priority, and execution lane internally\n\nWhen work ships or is rejected:\n\n- post the public resolution back to GitHub\n- mark the Linear task accordingly\n\n## Review Rules\n\n- Never merge from title, summary, or trust alone; use the full diff\n- External-source features should be rebuilt inside ECC when they are valuable but not self-contained\n- CI red means classify and fix or block; do not pretend it is merge-ready\n- If the real blocker is product direction, say so instead of hiding behind tooling\n\n## Output Format\n\nReturn:\n\n```text\nPUBLIC STATUS\n- issue \u002F PR state\n- CI \u002F review state\n\nCLASSIFICATION\n- merge \u002F port-rebuild \u002F close \u002F park\n- one-paragraph rationale\n\nLINEAR ACTION\n- create \u002F update \u002F no Linear item needed\n- project \u002F lane if applicable\n\nNEXT OPERATOR ACTION\n- exact next move\n```\n\n## Good Use Cases\n\n- \"Audit the open PR backlog and tell me what to merge vs rebuild\"\n- \"Map GitHub issues into our ECC 1.x and ECC 2.0 program lanes\"\n- \"Check whether this needs a Linear issue or should stay GitHub-only\"\n",{"name":5,"origin":45,"description":7},"ECC","main","b0f0a87593c578a7898eccaf1b363f7f87c1f99b","plugins\u002FColin4k1024\u002Ftsp\u002Fskills\u002Fproject-flow-ops",490,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 02:12:02",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill project-flow-ops",{"tool":62,"command":63},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill project-flow-ops",{"tool":65,"command":66},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill project-flow-ops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FColin4k1024\u002Ftsp\u002Fskills\u002Fproject-flow-ops\u002FSKILL.md",true,[],[71,79,86,93,119,143],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":78},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":78},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":78},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":40},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[100,101,102,103,104,105,106,107,108,109,110,23,111,112,113,114,115,116,117,118],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":40},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[126,127,128,114,129,130,131,132,133,134,135,136,137,138,105,139,21,140,141,142],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","session","end","reflection",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":160,"publishedAt":40},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[149,154,157],{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":155,"categoryName":156,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":158,"categoryName":159,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000010","后端与接口",[145,161,162,163,164,165,166,21,167,106,168,169,170,171,23,172,173,174,175,176],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]