[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6QJ2FPZM7RT25S6XJXZ4WPX":3,"skill-same:01M6QJ2FPZM7RT25S6XJXZ4WPX":69},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":14,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6QJ2FPZM7RT25S6XJXZ4WPX","linkedin-profile",null,"Use when someone wants their LinkedIn profile audited or rewritten — headline, About section, experience bullets, Featured, banner, recommendations — or says \"fix my headline\", \"my profile gets views but nothing happens\", \"optimize my LinkedIn profile\", \"what should my About section say\". Scores the headline on five dimensions, audits the whole profile 0-100 and ranks fixes by points per hour, and assembles an About section that survives the \"…see more\" fold.","Tashima-Tarsh\u002FDisha6.6","Tashima-Tarsh","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269906498?v=4","01M6PBH98X03XERH0HFT4PFB1P","NITISH KUMAR","01M6PBH9DA0M6KM3Z12P848F0K",0,"MIT","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Flinkedin-profile\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"linkedin","profile","linkedin profile","section","marketing","fixes","my","more","about","banner","recommendations","dimensions","but","optimize","Fold","say","use","fix","2026-11-10 10:12:30",false,"---\nname: linkedin-profile\ndescription: Use when someone wants their LinkedIn profile audited or rewritten — headline, About section, experience bullets, Featured, banner, recommendations — or says \"fix my headline\", \"my profile gets views but nothing happens\", \"optimize my LinkedIn profile\", \"what should my About section say\". Scores the headline on five dimensions, audits the whole profile 0-100 and ranks fixes by points per hour, and assembles an About section that survives the \"…see more\" fold.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-08-25\n---\n\n# LinkedIn Profile — audit, then rewrite the parts that pay\n\nA profile is not a CV. A CV is read by someone who already decided to consider you; a\nprofile is read by someone deciding whether to. Three readers, in descending volume: the\n**scanner** (three seconds, from your comment on someone else's post — sees photo and\nheadline only), the **evaluator** (forty seconds — headline, half the About, Featured), the\n**decider** (minutes — everything). Almost all traffic is the scanner. Almost all conversion\nis the decider.\n\n## Workflow\n\n**1. Audit before rewriting.** Ask them to describe their profile section by section, or\nhave them fill [`assets\u002Fprofile_worksheet.md`](assets\u002Fprofile_worksheet.md), then:\n\n```bash\npython3 scripts\u002Fprofile_completeness_auditor.py --input profile.json --output human\n```\n\nExit 0 STRONG \u002F 2 INCOMPLETE \u002F 3 WEAK. It ranks every gap by **points per hour** and prints\na first-hour plan — usually Featured, Open To, and skills, which cost minutes and recover\nreal points. Start there, not with the About section they wanted to agonise over.\n\n**2. Headline next — it is the only string that travels.** It rides along with every comment,\nsearch result, and invitation.\n\n```bash\npython3 scripts\u002Fheadline_scorer.py --headline \"...\" --output human\n```\n\nFive dimensions at 20 points: audience, outcome, proof, searchability, clarity. Exit 0 SHIP\n(≥75) \u002F 2 SHARPEN \u002F 3 REWRITE. It also checks the 220-character cap and whether the first\n~60 characters — the part that survives in search results and invitation previews — carry\nanything.\n\nIterate here. Two or three passes is normal; the stop condition is exit 0, or the user\nsaying they would say it out loud to a peer.\n\n**3. About section — write to the fold.** LinkedIn collapses it after roughly 265-300\ncharacters. Collect the five parts from the user, then assemble:\n\n```bash\npython3 scripts\u002Fabout_section_builder.py --input about.json --output human\n```\n\nIt refuses a fold that cuts mid-sentence, a fold carrying no audience and no proof, a\nmissing call to action, and anything over 2,600 characters.\n\n**4. Experience, Featured, recommendations.** Rewrite duty lists as outcomes. Pin one\nartifact a stranger could evaluate in sixty seconds. Ask for two specific recommendations by\nnaming the project and offering a first draft.\n\n## Rules\n\n- **Never invent a credential, a metric, or a role.** Every number on a profile is checkable\n  by someone. If the proof does not exist, the claim is qualitative or it is absent.\n- **First person.** A profile in third person reads as a press release someone else wrote.\n- **The fold is the section.** Whatever sits above \"…see more\" is what most readers get.\n- **Front-load the headline.** The strongest segment first; everything after is a bonus.\n- **Do not fetch anything.** The user describes their own profile; nothing is scraped.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fheadline_scorer.py`](scripts\u002Fheadline_scorer.py) | Headline 0-100 on audience \u002F outcome \u002F proof \u002F searchability \u002F clarity, plus the 220-char cap and front-load check. |\n| [`scripts\u002Fprofile_completeness_auditor.py`](scripts\u002Fprofile_completeness_auditor.py) | Whole profile 0-100 across 14 weighted checks; fixes ranked by points per hour with a first-hour plan. |\n| [`scripts\u002Fabout_section_builder.py`](scripts\u002Fabout_section_builder.py) | Assembles the About section from named parts and refuses a broken fold, a missing CTA, or an over-length section. |\n\n## References and assets\n\n- [`references\u002Fprofile_architecture.md`](references\u002Fprofile_architecture.md) — what each section is for, and the three readers (7 sources)\n- [`references\u002Fheadline_and_positioning.md`](references\u002Fheadline_and_positioning.md) — the 220 characters that follow you everywhere (7 sources)\n\n- [`assets\u002Fprofile_worksheet.md`](assets\u002Fprofile_worksheet.md) — fillable section-by-section worksheet\n- [`assets\u002Fexample_profile.json`](assets\u002Fexample_profile.json) — input shape for the auditor\n\n## Distinct from\n\n- **`linkedin-strategy`** — what to post and how often. This is who you are before you post.\n  If the audience answer is fuzzy, run `positioning_brief.py` there first; the headline\n  falls out of a good brief in ten minutes.\n- **`product-team\u002F`, `c-level-advisor\u002F`** — career and role strategy. This writes the profile,\n  not the career plan.\n\n---\n\n**Version:** 1.0.0\n","# LinkedIn Profile — audit, then rewrite the parts that pay\n\nA profile is not a CV. A CV is read by someone who already decided to consider you; a\nprofile is read by someone deciding whether to. Three readers, in descending volume: the\n**scanner** (three seconds, from your comment on someone else's post — sees photo and\nheadline only), the **evaluator** (forty seconds — headline, half the About, Featured), the\n**decider** (minutes — everything). Almost all traffic is the scanner. Almost all conversion\nis the decider.\n\n## Workflow\n\n**1. Audit before rewriting.** Ask them to describe their profile section by section, or\nhave them fill [`assets\u002Fprofile_worksheet.md`](assets\u002Fprofile_worksheet.md), then:\n\n```bash\npython3 scripts\u002Fprofile_completeness_auditor.py --input profile.json --output human\n```\n\nExit 0 STRONG \u002F 2 INCOMPLETE \u002F 3 WEAK. It ranks every gap by **points per hour** and prints\na first-hour plan — usually Featured, Open To, and skills, which cost minutes and recover\nreal points. Start there, not with the About section they wanted to agonise over.\n\n**2. Headline next — it is the only string that travels.** It rides along with every comment,\nsearch result, and invitation.\n\n```bash\npython3 scripts\u002Fheadline_scorer.py --headline \"...\" --output human\n```\n\nFive dimensions at 20 points: audience, outcome, proof, searchability, clarity. Exit 0 SHIP\n(≥75) \u002F 2 SHARPEN \u002F 3 REWRITE. It also checks the 220-character cap and whether the first\n~60 characters — the part that survives in search results and invitation previews — carry\nanything.\n\nIterate here. Two or three passes is normal; the stop condition is exit 0, or the user\nsaying they would say it out loud to a peer.\n\n**3. About section — write to the fold.** LinkedIn collapses it after roughly 265-300\ncharacters. Collect the five parts from the user, then assemble:\n\n```bash\npython3 scripts\u002Fabout_section_builder.py --input about.json --output human\n```\n\nIt refuses a fold that cuts mid-sentence, a fold carrying no audience and no proof, a\nmissing call to action, and anything over 2,600 characters.\n\n**4. Experience, Featured, recommendations.** Rewrite duty lists as outcomes. Pin one\nartifact a stranger could evaluate in sixty seconds. Ask for two specific recommendations by\nnaming the project and offering a first draft.\n\n## Rules\n\n- **Never invent a credential, a metric, or a role.** Every number on a profile is checkable\n  by someone. If the proof does not exist, the claim is qualitative or it is absent.\n- **First person.** A profile in third person reads as a press release someone else wrote.\n- **The fold is the section.** Whatever sits above \"…see more\" is what most readers get.\n- **Front-load the headline.** The strongest segment first; everything after is a bonus.\n- **Do not fetch anything.** The user describes their own profile; nothing is scraped.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fheadline_scorer.py`](scripts\u002Fheadline_scorer.py) | Headline 0-100 on audience \u002F outcome \u002F proof \u002F searchability \u002F clarity, plus the 220-char cap and front-load check. |\n| [`scripts\u002Fprofile_completeness_auditor.py`](scripts\u002Fprofile_completeness_auditor.py) | Whole profile 0-100 across 14 weighted checks; fixes ranked by points per hour with a first-hour plan. |\n| [`scripts\u002Fabout_section_builder.py`](scripts\u002Fabout_section_builder.py) | Assembles the About section from named parts and refuses a broken fold, a missing CTA, or an over-length section. |\n\n## References and assets\n\n- [`references\u002Fprofile_architecture.md`](references\u002Fprofile_architecture.md) — what each section is for, and the three readers (7 sources)\n- [`references\u002Fheadline_and_positioning.md`](references\u002Fheadline_and_positioning.md) — the 220 characters that follow you everywhere (7 sources)\n\n- [`assets\u002Fprofile_worksheet.md`](assets\u002Fprofile_worksheet.md) — fillable section-by-section worksheet\n- [`assets\u002Fexample_profile.json`](assets\u002Fexample_profile.json) — input shape for the auditor\n\n## Distinct from\n\n- **`linkedin-strategy`** — what to post and how often. This is who you are before you post.\n  If the audience answer is fuzzy, run `positioning_brief.py` there first; the headline\n  falls out of a good brief in ten minutes.\n- **`product-team\u002F`, `c-level-advisor\u002F`** — career and role strategy. This writes the profile,\n  not the career plan.\n\n---\n\n**Version:** 1.0.0\n",{"name":5,"license":15,"metadata":42,"description":7},{"author":43,"updated":44,"version":45,"category":23},"Alireza Rezvani",1787616000000,"1.0.0","main","0da4485785ee599388900be50db1635489d53056",".agents\u002Fskills\u002Flinkedin-profile","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6","https:\u002F\u002Fdisha6.6.thenitishkr.in\u002F","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh","www.thenitishkr","thenitishkr | AI • Cyber-security • Research\r\n","2026-11-08 03:33:25",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add Tashima-Tarsh\u002FDisha6.6 --skill linkedin-profile",{"tool":61,"command":62},"bunx","bunx skills add Tashima-Tarsh\u002FDisha6.6 --skill linkedin-profile",{"tool":64,"command":65},"pnpm","pnpm dlx skills add Tashima-Tarsh\u002FDisha6.6 --skill linkedin-profile","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Flinkedin-profile\u002FSKILL.md",true,[],[70,102,126,153,178,202],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":81,"publishedAt":37},"01M6QRD07D4TGNDK6VJ4EHF8BV","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[76],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000016","图像与多媒体","SCENARIO","使用场景",[82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101],"youtube full","youtube","full","transcript","search","monitoring","data","Video","Audio","list","files","do","get","age","trigger","URL","for","browsing","request","youtube transcripts",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":37},"01M6QRCJ3112VYPA97YG7KGMC2","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[109,110,111,112,86,113,114,115,116,117,118,119,120,121,35,122,123,124,125,98],"twitter","x twitter growth","growth","research","content","engineering","plan","web search","competitors","analyze","engine","write","strategy","platform","grow","posting","competitive",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":135,"publishedAt":37},"01M6QRBN3EHQNJY42RERP7A149","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发",[136,120,137,138,139,140,141,142,35,143,144,46,145,146,147,148,149,150,151,152],"write a skill","github","create","https","productivity","matt pocock","direct","example","build","new skill","structure","new agent","resources","with","tree","progressive disclosure","author",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":159,"publishedAt":37},"01M6QRB6G8P33PNGAF9Y69EJ9T","wrap-up","Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says \"wrap up\", \"close this out\", \"what do I own now\", \"give me the summary\", \"recap the agent\", or when the orchestrator routes phase=wrap-up. primitives_inventory.py tables everything owned (agent, environment, session, memory, outcome, deployment); overview_page.py regenerates a self-contained .\u002Fmy-agent\u002Fagent-overview.html; upgrade_suggester.py ranks the next moves from recorded deferrals plus standing hardening steps. Companion to run-without-you; the last stop before phase=done.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[160,161,162,163,164,165,166,167,168,35,169,93,170,171,172,173,174,175,176,177],"wrap up","up","wrap","gemini","deployment","run","file","hardening","closeout","stop","upgrade","founder","close","companion","you","tables","directions","phase",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":185,"publishedAt":37},"01M6QRA5AYC1RBFZ39GTWGS3N8","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[184],{"categoryNo":133,"categoryName":134,"taxonomyType":79,"taxonomyTypeDesc":80},[186,187,188,189,190,138,165,191,192,193,194,195,120,196,92,197,198,199,200,201],"workflow","workflow builder","builder","design","workflows","code","orchestrate","pipeline","loop","multi-agent","context","across","fresh","scripts","judge","claude code workflow",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":208,"publishedAt":37},"01M6QR7QMCZESKQA0ERW1E657M","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FTashima-Tarsh\u002FDisha6.6\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[209,210,211,212,213,214,215,216,217,194,218,219,220,221,222,223,94,224,225,177],"review","weekly review","weekly","deterministic scripts","reflect","feeds","inventory","open","team","projects","project-management","scanner","conversation","back","project","sprint","cadence"]