[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKV7GKAXPVFDBFRKDVSH7R":3,"skill-same:01M6MKV7GKAXPVFDBFRKDVSH7R":68},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6MKV7GKAXPVFDBFRKDVSH7R","fix-my-linkedin-profile",null,"Go through headline, about and featured in the order a visitor reads them, and rewrite whichever one is losing the click. Use when someone asks for a profile review, has a new role or a new offer, says their profile gets views and nothing else, or wants their headline rewritten. Do not stuff keywords, do not promise search placement, and do not rewrite the parts that are already working.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fprateeks367\u002Fvoicemoat-skills\u002Fskills\u002Ffix-my-linkedin-profile\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"linkedin","profile","fix","linkedin profile","fix my linkedin profile","my","click","new","when","parts","for","role","about","rewrite","review","promise","do","use","search","go","2026-11-10 10:12:30",false,"---\nname: fix-my-linkedin-profile\ndescription: Go through headline, about and featured in the order a visitor reads them, and rewrite whichever one is losing the click. Use when someone asks for a profile review, has a new role or a new offer, says their profile gets views and nothing else, or wants their headline rewritten. Do not stuff keywords, do not promise search placement, and do not rewrite the parts that are already working.\n---\n\n# Fix my LinkedIn profile\n\nA profile is read in a fixed order by somebody who has already decided to be\ncurious. They saw a post or a comment, they clicked the name, and now they are\ndeciding in a few seconds whether this person is worth following.\n\nMost profiles answer a different question. They are written as a CV, for a\nrecruiter, in the third person, and the visitor who arrived from a post is not\nthat reader.\n\n## Step 1: work out who lands here, and from where\n\nThe arrival changes what the first line has to do:\n\n- **From a post or a comment.** They liked one thing you said. The profile has\n  to tell them whether there is more of it.\n- **From search.** They have a problem and are checking whether you solve it.\n- **From a message or an introduction.** They are checking whether to reply.\n- **From your own link.** They were sent, and the profile is a landing page.\n\nAsk which of these dominates before rewriting anything.\n\n## Step 2: the headline\n\nThis is the only part that travels. It sits under your name on every post and\nevery comment you leave, so it is read far more often than the profile itself.\n\nIt has two jobs: say what you do in the words the reader uses, and give them a\nreason to click. Common failures:\n\n- The job title alone, which means nothing outside the company\n- A row of nouns separated by pipes, which reads as a search query\n- An abstraction about helping people unlock their potential\n- Keywords packed in until the line stops being a sentence\n\nTest it by reading it aloud directly after the person's name. If it does not\nsurvive being said out loud, it will not survive a feed.\n\n## Step 3: the first two lines of About\n\nEverything after them is behind \"see more\", and most About sections open with a\nwarm-up paragraph nobody gets past. Those two lines carry the whole section.\n\nThey should say who you help and what changes. Not your career history, which\nis what the experience section is for.\n\n## Step 4: the rest of About\n\nIn this order, in first person, in actual sentences: who you work with, what\nchanges for them, the proof, and what to do next.\n\nProof means something checkable. A number you can source, a name you have\npermission to use, a thing somebody can go and read. Adjectives are not proof.\n\n## Step 5: featured\n\nThree items at most, each earning its slot. Ask one question: if a stranger\nread exactly one thing here, which would you want it to be? Then check whether\nthat thing is first.\n\n## Step 6: say what to leave alone\n\nName the parts that are already working and say why. A review that rewrites\neverything is not a review, and it usually ends with a profile that sounds less\nlike the person than the one they started with.\n\n## What this will not do\n\nIt will not promise search placement. LinkedIn does not publish how its search\nranks people, and anyone quoting you a formula for it is guessing.\n\nIt will not stuff keywords. A headline written for a matching algorithm reads\nexactly like one to the human who arrived from a post, and that human is the\none who was going to follow you.\n\n## What changes when VoiceMoat is connected\n\nA profile written in a voice the posts do not share is the mismatch a visitor\nnotices first:\n\n- `get_voice_profile` gives your LinkedIn register, so the About section sounds\n  like the post that brought them here.\n- `get_voice_insights` shows the subjects and patterns you actually publish on,\n  which is usually a sharper answer to \"what do you do\" than the one people\n  give when asked directly.\n- `score_voice_match` scores the rewritten About against your profile, which\n  catches the drift into brochure voice that this exercise invites.\n\nVoiceMoat also runs three free LinkedIn profile tools at voicemoat.com\u002Ftools: a\nheadline analyzer, a headline generator and a summary generator. No account is\nneeded for those either.\n\nVoiceMoat is at voicemoat.com. The connector needs the Pro or Enterprise plan.\n","# Fix my LinkedIn profile\n\nA profile is read in a fixed order by somebody who has already decided to be\ncurious. They saw a post or a comment, they clicked the name, and now they are\ndeciding in a few seconds whether this person is worth following.\n\nMost profiles answer a different question. They are written as a CV, for a\nrecruiter, in the third person, and the visitor who arrived from a post is not\nthat reader.\n\n## Step 1: work out who lands here, and from where\n\nThe arrival changes what the first line has to do:\n\n- **From a post or a comment.** They liked one thing you said. The profile has\n  to tell them whether there is more of it.\n- **From search.** They have a problem and are checking whether you solve it.\n- **From a message or an introduction.** They are checking whether to reply.\n- **From your own link.** They were sent, and the profile is a landing page.\n\nAsk which of these dominates before rewriting anything.\n\n## Step 2: the headline\n\nThis is the only part that travels. It sits under your name on every post and\nevery comment you leave, so it is read far more often than the profile itself.\n\nIt has two jobs: say what you do in the words the reader uses, and give them a\nreason to click. Common failures:\n\n- The job title alone, which means nothing outside the company\n- A row of nouns separated by pipes, which reads as a search query\n- An abstraction about helping people unlock their potential\n- Keywords packed in until the line stops being a sentence\n\nTest it by reading it aloud directly after the person's name. If it does not\nsurvive being said out loud, it will not survive a feed.\n\n## Step 3: the first two lines of About\n\nEverything after them is behind \"see more\", and most About sections open with a\nwarm-up paragraph nobody gets past. Those two lines carry the whole section.\n\nThey should say who you help and what changes. Not your career history, which\nis what the experience section is for.\n\n## Step 4: the rest of About\n\nIn this order, in first person, in actual sentences: who you work with, what\nchanges for them, the proof, and what to do next.\n\nProof means something checkable. A number you can source, a name you have\npermission to use, a thing somebody can go and read. Adjectives are not proof.\n\n## Step 5: featured\n\nThree items at most, each earning its slot. Ask one question: if a stranger\nread exactly one thing here, which would you want it to be? Then check whether\nthat thing is first.\n\n## Step 6: say what to leave alone\n\nName the parts that are already working and say why. A review that rewrites\neverything is not a review, and it usually ends with a profile that sounds less\nlike the person than the one they started with.\n\n## What this will not do\n\nIt will not promise search placement. LinkedIn does not publish how its search\nranks people, and anyone quoting you a formula for it is guessing.\n\nIt will not stuff keywords. A headline written for a matching algorithm reads\nexactly like one to the human who arrived from a post, and that human is the\none who was going to follow you.\n\n## What changes when VoiceMoat is connected\n\nA profile written in a voice the posts do not share is the mismatch a visitor\nnotices first:\n\n- `get_voice_profile` gives your LinkedIn register, so the About section sounds\n  like the post that brought them here.\n- `get_voice_insights` shows the subjects and patterns you actually publish on,\n  which is usually a sharper answer to \"what do you do\" than the one people\n  give when asked directly.\n- `score_voice_match` scores the rewritten About against your profile, which\n  catches the drift into brochure voice that this exercise invites.\n\nVoiceMoat also runs three free LinkedIn profile tools at voicemoat.com\u002Ftools: a\nheadline analyzer, a headline generator and a summary generator. No account is\nneeded for those either.\n\nVoiceMoat is at voicemoat.com. The connector needs the Pro or Enterprise plan.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fprateeks367\u002Fvoicemoat-skills\u002Fskills\u002Ffix-my-linkedin-profile",483,"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-13 02:16:32",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fix-my-linkedin-profile",{"tool":60,"command":61},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fix-my-linkedin-profile",{"tool":63,"command":64},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill fix-my-linkedin-profile","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fprateeks367\u002Fvoicemoat-skills\u002Fskills\u002Ffix-my-linkedin-profile\u002FSKILL.md",true,[],[69,77,84,91,115,139],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":76},"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":76},"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":76},"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":39},"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",[],[37,98,99,100,101,102,103,104,21,105,106,27,107,108,109,110,111,112,113,114],"deja search","never","error","ready","memory","re","decide","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":39},"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",[],[122,123,33,110,124,125,126,127,128,129,130,131,132,133,102,134,135,136,137,138],"deja reflect","reflect","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":156,"publishedAt":39},"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",[145,150,153],{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",{"categoryNo":151,"categoryName":152,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":154,"categoryName":155,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000010","后端与接口",[141,157,158,159,160,161,162,135,163,103,164,165,166,167,27,168,169,170,171,172],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]