[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70XTEEB69DDBPWG2FAWHAAZ":3,"skill-same:01M70XTEEB69DDBPWG2FAWHAAZ":63},{"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":28,"linkOnly":29,"markdownContent":30,"markdownBody":31,"frontMatter":32,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M70XTEEB69DDBPWG2FAWHAAZ","actera-connect",null,"Connect this Codex installation to an Actera agent through administrator browser approval, or with a setup code from Actera.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1559,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FActera-AI\u002Factera-codex\u002Fskills\u002Factera-connect\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27],"connect","actera connect","codex","setup","code","browser","approval","installation","with","2026-11-10 10:12:30",false,"---\nname: actera-connect\ndescription: Connect this Codex installation to an Actera agent through administrator browser approval, or with a setup code from Actera.\n---\n\nConnect Actera without asking for or displaying a machine key.\n\nThe Actera plugin's command line is `bin\u002Factera-hook.mjs` in the plugin folder, two levels above the folder that holds this `SKILL.md`. Run it with Node.js using its absolute path, from a terminal command with a ten-minute timeout. Keep it attached until it prints its result.\n\n- If the person gave a setup code from Actera (16 letters and digits, usually in four groups such as `7AHV-F8T0-M349-HPF7`), run `node \"\u003Cplugin folder>\u002Fbin\u002Factera-hook.mjs\" connect --setup-code \u003Ccode>`. It connects to the agent an administrator made the code for, with no browser page. A code works once and expires after 30 minutes; if it fails, tell the person to get a new code from Actera.\n- Otherwise run `node \"\u003Cplugin folder>\u002Fbin\u002Factera-hook.mjs\" connect`. It opens an Actera page in the browser and waits for an administrator to approve the connection. Tell the person to check that the code on that page matches the one the command prints. The page suggests a new agent named Codex; an administrator can rename it or choose an existing agent.\n- Add `--reconnect` only when the person asks to reconnect.\n\nThe plugin includes its Actera API endpoint. Do not ask for an API URL, agent ID, key, policies or fallback behavior. Never request, print or pass a machine key.\n\nBefore connecting, tell the person what the plugin sends: each tool call's name and inputs, after it redacts sensitive fields and scans for secrets with the bundled Gitleaks. Detection is best effort; ordinary commands and file paths stay visible. Prompts and tool output are not sent.\n\nAfter it connects, report the mode and the evaluation-failure choice the command printed. Monitoring (the default) records every tool call and never blocks. Enforcing blocks what policies deny and holds calls that need approval until a reviewer decides in Actera, Slack or email, or in Codex: the first held call offers to link Codex to the person's Actera account, after which Codex asks them to allow or deny each held call. `$actera-mode` changes either setting.\n\nThen tell the person the one step Codex needs from them: open `\u002Fhooks` in Codex, trust the two Actera hooks, and start a new session. Codex does not run a plugin's hooks until they are trusted, and asks again after every plugin update. Until then no tool call is checked. `$actera-status` shows whether the hooks have run. Do not describe connecting alone as proof that tool calls reach Actera.\n","Connect Actera without asking for or displaying a machine key.\n\nThe Actera plugin's command line is `bin\u002Factera-hook.mjs` in the plugin folder, two levels above the folder that holds this `SKILL.md`. Run it with Node.js using its absolute path, from a terminal command with a ten-minute timeout. Keep it attached until it prints its result.\n\n- If the person gave a setup code from Actera (16 letters and digits, usually in four groups such as `7AHV-F8T0-M349-HPF7`), run `node \"\u003Cplugin folder>\u002Fbin\u002Factera-hook.mjs\" connect --setup-code \u003Ccode>`. It connects to the agent an administrator made the code for, with no browser page. A code works once and expires after 30 minutes; if it fails, tell the person to get a new code from Actera.\n- Otherwise run `node \"\u003Cplugin folder>\u002Fbin\u002Factera-hook.mjs\" connect`. It opens an Actera page in the browser and waits for an administrator to approve the connection. Tell the person to check that the code on that page matches the one the command prints. The page suggests a new agent named Codex; an administrator can rename it or choose an existing agent.\n- Add `--reconnect` only when the person asks to reconnect.\n\nThe plugin includes its Actera API endpoint. Do not ask for an API URL, agent ID, key, policies or fallback behavior. Never request, print or pass a machine key.\n\nBefore connecting, tell the person what the plugin sends: each tool call's name and inputs, after it redacts sensitive fields and scans for secrets with the bundled Gitleaks. Detection is best effort; ordinary commands and file paths stay visible. Prompts and tool output are not sent.\n\nAfter it connects, report the mode and the evaluation-failure choice the command printed. Monitoring (the default) records every tool call and never blocks. Enforcing blocks what policies deny and holds calls that need approval until a reviewer decides in Actera, Slack or email, or in Codex: the first held call offers to link Codex to the person's Actera account, after which Codex asks them to allow or deny each held call. `$actera-mode` changes either setting.\n\nThen tell the person the one step Codex needs from them: open `\u002Fhooks` in Codex, trust the two Actera hooks, and start a new session. Codex does not run a plugin's hooks until they are trusted, and asks again after every plugin update. Until then no tool call is checked. `$actera-status` shows whether the hooks have run. Do not describe connecting alone as proof that tool calls reach Actera.\n",{"name":5,"description":7},"main","f620abaff09061f8c8b1f1559dca3fdd031a32e5","plugins\u002FActera-AI\u002Factera-codex\u002Fskills\u002Factera-connect",474,"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-11 14:40:14",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill actera-connect",{"tool":49,"command":50},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill actera-connect",{"tool":52,"command":53},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill actera-connect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FActera-AI\u002Factera-codex\u002Fskills\u002Factera-connect\u002FSKILL.md",true,[57],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"agents\u002Fopenai.yaml","REFERENCE","参考文档",168,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FActera-AI\u002Factera-codex\u002Fskills\u002Factera-connect\u002Fagents\u002Fopenai.yaml",[64,72,79,86,113,137],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":71},"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":71},"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":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":71},"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":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":28},"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",[],[93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","when","you","done","reviewer","io","change","cli","merge","past",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":28},"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",[],[120,121,122,108,27,123,124,125,126,127,128,129,130,131,98,132,133,134,135,136],"deja reflect","reflect","review","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":154,"publishedAt":28},"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",[143,148,151],{"categoryNo":144,"categoryName":145,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":149,"categoryName":150,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":152,"categoryName":153,"taxonomyType":146,"taxonomyTypeDesc":147},"01JBSEEDCAT000000000000010","后端与接口",[139,155,156,157,158,159,160,133,161,99,162,163,164,165,104,166,167,168,169,170],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]