[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BR96JSQGR8QGSKKBEKDR4D":3,"skill-same:01M7BR96JSQGR8QGSKKBEKDR4D":49},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7BR96JSQGR8QGSKKBEKDR4D","linkedin-analytics",null,"Use when someone wants to understand their own LinkedIn numbers — which posts worked, why reach dropped, whether a pattern is real, or how to test a hypothesis. Triggers on \"why did my reach drop\", \"what's working on my LinkedIn\", \"analyze my posts\", \"do carousels do better for me\", \"should I test this\", \"LinkedIn analytics\". Reads your own exported post data, reports medians and outlier bands, tests candidate patterns against a permutation null, and sizes a real experiment — refusing to conclude anything below 10 posts.","azhri1990\u002Fproject-genesis","azhri1990","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281207543?v=4","01M7BMC0WHXB2ZA9SH1PFJDYNS","Nashriq Mokhtar","01M7BMC0XAE6SV0VTKWP3EMFGZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.gemini\u002Fskills\u002Flinkedin-analytics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: linkedin-analytics\ndescription: Use when someone wants to understand their own LinkedIn numbers — which posts worked, why reach dropped, whether a pattern is real, or how to test a hypothesis. Triggers on \"why did my reach drop\", \"what's working on my LinkedIn\", \"analyze my posts\", \"do carousels do better for me\", \"should I test this\", \"LinkedIn analytics\". Reads your own exported post data, reports medians and outlier bands, tests candidate patterns against a permutation null, and sizes a real experiment — refusing to conclude anything below 10 posts.\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-08-25\n---\n\n# LinkedIn Analytics — describe honestly, then refuse to over-conclude\n\nThe characteristic sentence of LinkedIn analytics is \"carousels do 3x better for me\", built\non four posts. With engagement as heavy-tailed as it is, four posts will show a 3x difference\nbetween almost any two groups you care to define. These three scripts stop that sentence\nbecoming a strategy.\n\n**Your own data only.** Nothing is fetched; scraping post or profile data is prohibited by\nUser Agreement §8.2 and none of this analysis needs it.\n\n## Workflow\n\n**1. Get the export.** LinkedIn Analytics → Post impressions → Export, or Settings → Data\nprivacy → Get a copy of your data. CSV and JSON both work.\n\n**2. Describe it.** Exit 0 analysed \u002F 2 below the 10-post floor, descriptive only \u002F 3\nunusable. Reports median and MAD rather than mean and standard deviation — one breakout post\nmakes a mean describe a distribution none of your posts belong to — plus Tukey percentile\nbands and a 1.5×IQR breakout threshold, so \"this did well\" has a number behind it.\n\n```bash\npython3 scripts\u002Fpost_performance_analyzer.py --input posts.csv --csv --output human\n```\n\n**3. Test the pattern they think they see.**\n\n```bash\npython3 scripts\u002Fpattern_miner.py --input posts.json --output human\n```\n\nExit 0 something survived \u002F 2 nothing survived \u002F 3 under 10 posts. Four gates: 5 posts in and\n5 out; a 15% relative difference in medians; beating 90% of 2,000 seeded label shuffles; and\na multiple-comparisons accounting of how many candidates would pass on noise alone.\n\n**\"Nothing survived\" is the most common honest answer and it is a real finding.** Report it\nas one. Do not soften it into a hedge that reads like a conclusion.\n\n**4. Turn a survivor into a test.**\n\n```bash\npython3 scripts\u002Fexperiment_planner.py --hypothesis \"...\" --variable \"...\" \\\n  --cv 0.45 --effect 0.30 --posts-per-week 2 --max-weeks 12 --output human\n```\n\nCV comes from step 2: `1.4826 * MAD \u002F median`. Exit 0 feasible \u002F 2 too long, with the minimum\ndetectable effect in their window \u002F 3 refused. It will frequently say the test needs more\nposts than a quarter allows — **that is the honest answer**, and more useful than a confident\nconclusion from retrospective data.\n\n## Rules\n\n- **Under 10 posts, describe; do not conclude.** Say so plainly.\n- **A pattern in past posts is a hypothesis.** Retrospective data is confounded — you made\n  carousels when you had structured material, on topics you knew best, in weeks you had time.\n  No statistics on the same data removes that.\n- **Never benchmark against someone else's numbers.** Different denominator, different\n  audience, usually a vendor's sample.\n- **Follower count is not a success metric.** Track inbound conversations, specific\n  references, invitations — the Tier 1 metrics you count by hand.\n- **Report the confidence level.** LinkedIn-official 🟢, third-party study 🟡, folklore 🔴.\n- **One good post is not evidence.** It is the most common cause of a strategy change and the\n  least informative event available.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fpost_performance_analyzer.py`](scripts\u002Fpost_performance_analyzer.py) | Median\u002FMAD, percentile bands, IQR outlier fence, per-post BREAKOUT→DUD classification; refuses conclusions below 10 posts. |\n| [`scripts\u002Fpattern_miner.py`](scripts\u002Fpattern_miner.py) | Four-gate permutation test with multiple-comparisons accounting; reports why every rejected candidate failed. |\n| [`scripts\u002Fexperiment_planner.py`](scripts\u002Fexperiment_planner.py) | Sizes a two-arm posting experiment, names the confounds to hold constant, and writes the falsification condition before the first post. |\n\n## References and assets\n\n- [`references\u002Flinkedin_metrics_canon.md`](references\u002Flinkedin_metrics_canon.md) — what each number is, what it is not, and which three tiers to track (7 sources)\n- [`references\u002Fevidence_thresholds.md`](references\u002Fevidence_thresholds.md) — the four gates, forking paths, and the uncomfortable arithmetic of LinkedIn A\u002FB tests (7 sources)\n\n- [`assets\u002Fexample_post_export.csv`](assets\u002Fexample_post_export.csv) — a 12-post export in the expected shape\n- [`assets\u002Fmeasurement_log_template.md`](assets\u002Fmeasurement_log_template.md) — the Tier 1 outcome log you keep by hand\n\n## Distinct from\n\n- **`marketing-skill\u002Fsocial-media-analyzer`** — cross-platform brand campaign reporting. This\n  is one person's own LinkedIn export, with refusals attached.\n- **`linkedin-strategy`** — decides what to do next. This says what happened.\n- **`product-team\u002Fexperiment-designer`** — product A\u002FB tests with real traffic; here n is\n  posts, and usually too small.\n\n---\n**Version:** 1.0.0\n","# LinkedIn Analytics — describe honestly, then refuse to over-conclude\n\nThe characteristic sentence of LinkedIn analytics is \"carousels do 3x better for me\", built\non four posts. With engagement as heavy-tailed as it is, four posts will show a 3x difference\nbetween almost any two groups you care to define. These three scripts stop that sentence\nbecoming a strategy.\n\n**Your own data only.** Nothing is fetched; scraping post or profile data is prohibited by\nUser Agreement §8.2 and none of this analysis needs it.\n\n## Workflow\n\n**1. Get the export.** LinkedIn Analytics → Post impressions → Export, or Settings → Data\nprivacy → Get a copy of your data. CSV and JSON both work.\n\n**2. Describe it.** Exit 0 analysed \u002F 2 below the 10-post floor, descriptive only \u002F 3\nunusable. Reports median and MAD rather than mean and standard deviation — one breakout post\nmakes a mean describe a distribution none of your posts belong to — plus Tukey percentile\nbands and a 1.5×IQR breakout threshold, so \"this did well\" has a number behind it.\n\n```bash\npython3 scripts\u002Fpost_performance_analyzer.py --input posts.csv --csv --output human\n```\n\n**3. Test the pattern they think they see.**\n\n```bash\npython3 scripts\u002Fpattern_miner.py --input posts.json --output human\n```\n\nExit 0 something survived \u002F 2 nothing survived \u002F 3 under 10 posts. Four gates: 5 posts in and\n5 out; a 15% relative difference in medians; beating 90% of 2,000 seeded label shuffles; and\na multiple-comparisons accounting of how many candidates would pass on noise alone.\n\n**\"Nothing survived\" is the most common honest answer and it is a real finding.** Report it\nas one. Do not soften it into a hedge that reads like a conclusion.\n\n**4. Turn a survivor into a test.**\n\n```bash\npython3 scripts\u002Fexperiment_planner.py --hypothesis \"...\" --variable \"...\" \\\n  --cv 0.45 --effect 0.30 --posts-per-week 2 --max-weeks 12 --output human\n```\n\nCV comes from step 2: `1.4826 * MAD \u002F median`. Exit 0 feasible \u002F 2 too long, with the minimum\ndetectable effect in their window \u002F 3 refused. It will frequently say the test needs more\nposts than a quarter allows — **that is the honest answer**, and more useful than a confident\nconclusion from retrospective data.\n\n## Rules\n\n- **Under 10 posts, describe; do not conclude.** Say so plainly.\n- **A pattern in past posts is a hypothesis.** Retrospective data is confounded — you made\n  carousels when you had structured material, on topics you knew best, in weeks you had time.\n  No statistics on the same data removes that.\n- **Never benchmark against someone else's numbers.** Different denominator, different\n  audience, usually a vendor's sample.\n- **Follower count is not a success metric.** Track inbound conversations, specific\n  references, invitations — the Tier 1 metrics you count by hand.\n- **Report the confidence level.** LinkedIn-official 🟢, third-party study 🟡, folklore 🔴.\n- **One good post is not evidence.** It is the most common cause of a strategy change and the\n  least informative event available.\n\n## Scripts\n\n| Script | Role |\n|---|---|\n| [`scripts\u002Fpost_performance_analyzer.py`](scripts\u002Fpost_performance_analyzer.py) | Median\u002FMAD, percentile bands, IQR outlier fence, per-post BREAKOUT→DUD classification; refuses conclusions below 10 posts. |\n| [`scripts\u002Fpattern_miner.py`](scripts\u002Fpattern_miner.py) | Four-gate permutation test with multiple-comparisons accounting; reports why every rejected candidate failed. |\n| [`scripts\u002Fexperiment_planner.py`](scripts\u002Fexperiment_planner.py) | Sizes a two-arm posting experiment, names the confounds to hold constant, and writes the falsification condition before the first post. |\n\n## References and assets\n\n- [`references\u002Flinkedin_metrics_canon.md`](references\u002Flinkedin_metrics_canon.md) — what each number is, what it is not, and which three tiers to track (7 sources)\n- [`references\u002Fevidence_thresholds.md`](references\u002Fevidence_thresholds.md) — the four gates, forking paths, and the uncomfortable arithmetic of LinkedIn A\u002FB tests (7 sources)\n\n- [`assets\u002Fexample_post_export.csv`](assets\u002Fexample_post_export.csv) — a 12-post export in the expected shape\n- [`assets\u002Fmeasurement_log_template.md`](assets\u002Fmeasurement_log_template.md) — the Tier 1 outcome log you keep by hand\n\n## Distinct from\n\n- **`marketing-skill\u002Fsocial-media-analyzer`** — cross-platform brand campaign reporting. This\n  is one person's own LinkedIn export, with refusals attached.\n- **`linkedin-strategy`** — decides what to do next. This says what happened.\n- **`product-team\u002Fexperiment-designer`** — product A\u002FB tests with real traffic; here n is\n  posts, and usually too small.\n\n---\n**Version:** 1.0.0\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1787616000000,"1.0.0","marketing","main","456c0680145b74fe0168cc63541f08eda89e53c0","claude-skills\u002F.gemini\u002Fskills\u002Flinkedin-analytics","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis","https:\u002F\u002Fgithub.com\u002Fazhri1990","2026-09-27 20:56:28",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add azhri1990\u002Fproject-genesis --skill linkedin-analytics",{"tool":41,"command":42},"bunx","bunx skills add azhri1990\u002Fproject-genesis --skill linkedin-analytics",{"tool":44,"command":45},"pnpm","pnpm dlx skills add azhri1990\u002Fproject-genesis --skill linkedin-analytics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002F.gemini\u002Fskills\u002Flinkedin-analytics\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7C0EZY9FK6JW3YAC7CN17KY","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7C0EA12FWRZTMG0N23HV68M","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"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":19},"01M7C0DXEHJKMKTB4N6B7MS4BT","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"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":19},"01M7C0DJM5ECEKZXTQA9G6YHQZ","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7C0D304Z7YX7J25R42N6W2T","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7C0CP1419VDF6SGCDY6ZRZV","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fazhri1990\u002Fproject-genesis\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]