[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJ4JG34YB57S85VPR7RTTT":3,"skill-same:01M6MJ4JG34YB57S85VPR7RTTT":81},{"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":23,"publishedAt":48,"linkOnly":49,"markdownContent":50,"markdownBody":51,"frontMatter":52,"refName":57,"commitSha":58,"skillDirectory":59,"forksCount":60,"repositoryHtmlUrl":61,"repositoryHomepageUrl":62,"ownerHtmlUrl":63,"ownerBlogUrl":64,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6MJ4JG34YB57S85VPR7RTTT","linkedin-account-brief",null,"Prepare a one-page account brief before a sales call, demo or meeting, with LinkedIn data from the LinkMCP connector. The brief covers the company and its recent posts, the people the user will meet and their posts, and shared connections. It also gives talking points and questions to ask. Use when the user asks to research a company or a person on LinkedIn before a call. Also use it when the user asks for call prep, meeting prep or an account brief with LinkedIn data. Reads LinkedIn data only and sends nothing.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1571,"MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flinkmcp-io\u002Flinkmcp\u002Fskills\u002Flinkedin-account-brief\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47],"account brief","brief","linkedin account brief","linkedin","shared","paid","when","Meet","company","one-page","posts","remote","people","call prep","MCP","Connector","ai client","only","ask","plan","server","meeting prep","search","mcp server","2026-11-10 10:12:30",false,"---\nname: linkedin-account-brief\ndescription: \"Prepare a one-page account brief before a sales call, demo or meeting, with LinkedIn data from the LinkMCP connector. The brief covers the company and its recent posts, the people the user will meet and their posts, and shared connections. It also gives talking points and questions to ask. Use when the user asks to research a company or a person on LinkedIn before a call. Also use it when the user asks for call prep, meeting prep or an account brief with LinkedIn data. Reads LinkedIn data only and sends nothing.\"\nlicense: MIT\ncompatibility: \"Needs the LinkMCP connector (remote MCP server) in the AI client. Some steps (company search by name, people search, shared connections) need a paid LinkMCP plan with a connected LinkedIn account.\"\nmetadata:\n  author: LinkMCP\n  version: \"1.0.0\"\n---\n\n# LinkedIn account brief\n\nMake a short brief that the user can read in two minutes before a call. Use only facts from the LinkMCP tools and from the user. Mark each guess as a guess.\n\n## Rules\n\n- This skill only reads. Do not send messages or connection requests. Do not post, comment or react.\n- If the user asks for an introduction message, write it in the chat as a draft. Do not send it. A send is a separate request, and it needs the user's approval of that exact message.\n- Do not make a LinkedIn URL from the name of a person. Ask the user for the URL, or use people search (step 4).\n- Do not look up email addresses or phone numbers. The brief does not need them.\n- LinkMCP lookups can use part of the monthly LinkMCP usage of the user. Do not request the same data two times.\n\n## Tools\n\nThis skill uses these LinkMCP tools. All of them only read: `linkedin_get_company`, `linkedin_get_company_posts`, `linkedin_get_profile`, `linkedin_get_person_posts`, `linkedin_search_people`, `linkedin_get_shared_connections`.\n\nYour client can show a tool name with a prefix, for example `mcp__linkmcp__linkedin_get_company`. Use the tool whose name ends with the name in this skill.\n\n## Steps\n\n1. Make sure that the LinkMCP tools are available, for example `linkedin_get_company`. If they are not available, stop and tell the user how to connect LinkMCP:\n   - With the LinkMCP plugin: connect the LinkMCP connector of the plugin and sign in. In Claude, the connector is on the Connectors tab of the plugin.\n   - Without the plugin: add LinkMCP as a remote MCP server with the URL `https:\u002F\u002Fapp.linkmcp.io\u002Fapi\u002Fmcp?ref=skills` and sign in. Setup steps for each AI client: https:\u002F\u002Fapp.linkmcp.io\u002Fdocs\u002Fquick-start\n2. Get the inputs. You need the company (the LinkedIn company URL is best, or the name), the person (LinkedIn profile URL), or both. If the user did not give the goal of the call, ask for it.\n3. Company:\n   - Call `linkedin_get_company` with `identifier` (a LinkedIn company URL, slug or ID). If you only know the name of the company, use `name` instead. A search by name needs a connected LinkedIn account. If that is not available, ask the user for the LinkedIn URL of the company.\n   - If you get a list of candidates, ask the user which company is correct.\n   - Call `linkedin_get_company_posts` one time. Use the posts of the last 90 days.\n4. People (up to 3 people, unless the user asks for more):\n   - For each LinkedIn profile URL, call `linkedin_get_profile`.\n   - For each person, call `linkedin_get_person_posts` one time. Use the posts of the last 90 days.\n   - If the user gives a role but no person, use `linkedin_search_people`. Put the role and the company name in `keywords`. Show the results and let the user select the person. This tool needs a connected LinkedIn account.\n5. Warm introductions (optional): for each person, call `linkedin_get_shared_connections`. This tool needs a connected LinkedIn account. If it is not available, write \"Not checked\" and the reason in the brief.\n6. Write the brief in the format below.\n\n## Brief format\n\nTitle: **\u003CCompany>: brief for \u003Cgoal of the call>** and the date of today.\n\n1. **Company:** what it does, industry, size, headquarters and website. One to three sentences.\n2. **Now:** three to five topics from the recent company posts. Give the date and the link of each post.\n3. **People:** for each person, the role, the time in the role, the background in one line, and the topics of the recent posts, with links.\n4. **Shared connections:** the names and how each person can help, or \"Not checked\" and the reason.\n5. **Talking points:** three to five points. Connect each point to a fact above.\n6. **Questions to ask:** three to five open questions.\n7. **Gaps:** the data that you could not find or check.\n\nKeep the brief under 400 words. Do not show raw tool output.\n\n## When a tool fails\n\n- If a tool needs a connected LinkedIn account or a paid plan, it tells you. Give that message to the user. Then continue with the other steps.\n- If a tool reports a limit or tells you to wait, do what it says. Do not call the tool again and again. If the wait is long, stop and tell the user.\n- If LinkMCP cannot find a profile or a company, ask the user for the exact LinkedIn URL.\n","# LinkedIn account brief\n\nMake a short brief that the user can read in two minutes before a call. Use only facts from the LinkMCP tools and from the user. Mark each guess as a guess.\n\n## Rules\n\n- This skill only reads. Do not send messages or connection requests. Do not post, comment or react.\n- If the user asks for an introduction message, write it in the chat as a draft. Do not send it. A send is a separate request, and it needs the user's approval of that exact message.\n- Do not make a LinkedIn URL from the name of a person. Ask the user for the URL, or use people search (step 4).\n- Do not look up email addresses or phone numbers. The brief does not need them.\n- LinkMCP lookups can use part of the monthly LinkMCP usage of the user. Do not request the same data two times.\n\n## Tools\n\nThis skill uses these LinkMCP tools. All of them only read: `linkedin_get_company`, `linkedin_get_company_posts`, `linkedin_get_profile`, `linkedin_get_person_posts`, `linkedin_search_people`, `linkedin_get_shared_connections`.\n\nYour client can show a tool name with a prefix, for example `mcp__linkmcp__linkedin_get_company`. Use the tool whose name ends with the name in this skill.\n\n## Steps\n\n1. Make sure that the LinkMCP tools are available, for example `linkedin_get_company`. If they are not available, stop and tell the user how to connect LinkMCP:\n   - With the LinkMCP plugin: connect the LinkMCP connector of the plugin and sign in. In Claude, the connector is on the Connectors tab of the plugin.\n   - Without the plugin: add LinkMCP as a remote MCP server with the URL `https:\u002F\u002Fapp.linkmcp.io\u002Fapi\u002Fmcp?ref=skills` and sign in. Setup steps for each AI client: https:\u002F\u002Fapp.linkmcp.io\u002Fdocs\u002Fquick-start\n2. Get the inputs. You need the company (the LinkedIn company URL is best, or the name), the person (LinkedIn profile URL), or both. If the user did not give the goal of the call, ask for it.\n3. Company:\n   - Call `linkedin_get_company` with `identifier` (a LinkedIn company URL, slug or ID). If you only know the name of the company, use `name` instead. A search by name needs a connected LinkedIn account. If that is not available, ask the user for the LinkedIn URL of the company.\n   - If you get a list of candidates, ask the user which company is correct.\n   - Call `linkedin_get_company_posts` one time. Use the posts of the last 90 days.\n4. People (up to 3 people, unless the user asks for more):\n   - For each LinkedIn profile URL, call `linkedin_get_profile`.\n   - For each person, call `linkedin_get_person_posts` one time. Use the posts of the last 90 days.\n   - If the user gives a role but no person, use `linkedin_search_people`. Put the role and the company name in `keywords`. Show the results and let the user select the person. This tool needs a connected LinkedIn account.\n5. Warm introductions (optional): for each person, call `linkedin_get_shared_connections`. This tool needs a connected LinkedIn account. If it is not available, write \"Not checked\" and the reason in the brief.\n6. Write the brief in the format below.\n\n## Brief format\n\nTitle: **\u003CCompany>: brief for \u003Cgoal of the call>** and the date of today.\n\n1. **Company:** what it does, industry, size, headquarters and website. One to three sentences.\n2. **Now:** three to five topics from the recent company posts. Give the date and the link of each post.\n3. **People:** for each person, the role, the time in the role, the background in one line, and the topics of the recent posts, with links.\n4. **Shared connections:** the names and how each person can help, or \"Not checked\" and the reason.\n5. **Talking points:** three to five points. Connect each point to a fact above.\n6. **Questions to ask:** three to five open questions.\n7. **Gaps:** the data that you could not find or check.\n\nKeep the brief under 400 words. Do not show raw tool output.\n\n## When a tool fails\n\n- If a tool needs a connected LinkedIn account or a paid plan, it tells you. Give that message to the user. Then continue with the other steps.\n- If a tool reports a limit or tells you to wait, do what it says. Do not call the tool again and again. If the wait is long, stop and tell the user.\n- If LinkMCP cannot find a profile or a company, ask the user for the exact LinkedIn URL.\n",{"name":5,"license":15,"metadata":53,"description":7,"compatibility":56},{"author":54,"version":55},"LinkMCP","1.0.0","Needs the LinkMCP connector (remote MCP server) in the AI client. Some steps (company search by name, people search, shared connections) need a paid LinkMCP plan with a connected LinkedIn account.","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Flinkmcp-io\u002Flinkmcp\u002Fskills\u002Flinkedin-account-brief",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":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-account-brief",{"tool":73,"command":74},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-account-brief",{"tool":76,"command":77},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill linkedin-account-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Flinkmcp-io\u002Flinkmcp\u002Fskills\u002Flinkedin-account-brief\u002FSKILL.md",true,[],[82,91,98,105,130,155],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":90},"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.","Apache-2.0","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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":90},"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":90},"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":48},"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",[],[46,112,113,114,115,116,117,118,119,120,121,30,122,123,124,125,126,127,128,129],"deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":48},"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",[],[137,138,139,125,140,141,142,143,144,145,146,147,148,149,116,150,151,152,153,154],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":86,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":168,"publishedAt":48},"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",[161,164,165],{"categoryNo":162,"categoryName":163,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":166,"categoryName":167,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[157,169,170,171,172,173,174,151,175,117,176,177,38,178,30,179,47,180,181,182],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","song","image","schedule","api","publish"]