[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76E83NE8MCFZJ75RGTHX2HX":3,"skill-same:01M76E83NE8MCFZJ75RGTHX2HX":54},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":38,"updatedAt":39,"install":40,"resources":53},"01M76E83NE8MCFZJ75RGTHX2HX","nmrglue",null,"Processes calibrated one-dimensional complex NMR free-induction decays with nmrglue into phased spectra, peak candidates, and signed integration regions. Use for raw 1D NMR processing, ppm-axis verification, apodization, Fourier transformation, manual phasing, baseline correction, or reproducible spectral integration.","bg-szy\u002FTOP-SKILLS","bg-szy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F106576190?v=4","01M73A4E8KPV67SFXRY8XZGNBX","ShuZhiyong","01M73A4E96MQ294MHM74TZBVQD",6,"MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fawesome-skills\u002Fnmrglue\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: nmrglue\ndescription: Processes calibrated one-dimensional complex NMR free-induction decays with nmrglue into phased spectra, peak candidates, and signed integration regions. Use for raw 1D NMR processing, ppm-axis verification, apodization, Fourier transformation, manual phasing, baseline correction, or reproducible spectral integration.\nlicense: MIT\ncompatibility: Requires Python 3.12+, nmrglue, NumPy 2+, and SciPy. Installation needs network access; processing is local and needs no credentials.\nmetadata:\n  version: \"1.1\"\n  skill-author: K-Dense Inc.\n  tested-package-version: \"0.12\"\n  last-reviewed: \"2026-10-01\"\n---\n\n# nmrglue: calibrated 1D FID processing\n\n## When to use\n\nUse for a uniformly sampled complex 1D FID whose acquisition parameters and complex\nfrequency convention are available. The helper produces a descending ppm spectrum,\npositive peak candidates, signed region integrals, and a reproducible processing report.\nIt does not identify compounds or assign resonances.\n\nThe executable accepts a NumPy `.npz` containing exactly one complex `fid` array or a\ncanonical 1D complex time-domain NMRPipe file. NMRPipe reading is tested with a synthetic\nwrite\u002Fread round trip, known-spectrum recovery, and a small upstream NMRPipe-generated\nbinary fixture. Experimental Bruker, Varian, and JEOL\nimports are **not verified by this suite**. For those formats, first inspect the relevant\nnmrglue reader and acquisition metadata. Opening a converted file does not validate the\noriginal acquisition decoding.\nRead [references\u002Facquisition-and-validation.md](references\u002Facquisition-and-validation.md)\nfor conversion boundaries, axis calibration, and quantitative limits.\n\n## Workflow\n\n1. Preserve the raw FID. Establish spectral width in Hz, positive observation frequency\n   in MHz, carrier in ppm, observed nucleus, and the sign convention from the acquisition\n   or a known reference. Determine whether digital-filter\u002Fgroup-delay removal has already\n   occurred. Do not infer these from array length or typical instrument defaults.\n2. Copy [assets\u002Fprocessing.json](assets\u002Fprocessing.json) and replace its synthetic example\n   values with the measured parameters and explicit processing choices. Its sign `-i`\n   means a resonance at offset `f = (ppm - carrier_ppm) * observation_mhz` has time\n   dependence `exp(-2*pi*i*f*t)`. Select `+i` only for the opposite convention; the helper\n   conjugates it before processing. Validate with a known reference peak.\n3. Choose nonnegative exponential line broadening (Hz), an even zero-filled size at\n   least as large as the acquired FID, first-point scaling, and phase angles.\n   Zero filling improves interpolation, not acquired spectral resolution.\n   First-point scaling `0.5` is suitable for the supplied causal synthetic example;\n   acquisition and prior preprocessing may require another value.\n4. Run the helper, inspect the real and imaginary spectra, and revise manual phase if\n   needed. `phase0_deg + phase1_deg * index \u002F zero_fill_points` is applied after FT;\n   index zero is the high-ppm edge. There is no implicit pivot or automatic phase estimate.\n5. Only fit a linear baseline when explicitly supplied ppm regions are signal-free.\n   Set `baseline` to `linear` and add `baseline_regions_ppm` containing at least two\n   regions. Inspect residuals and broad peaks; fitting through signals biases integrals.\n6. Compare peak positions with references, inspect peak candidates for artifacts, and\n   integrate specified regions. Report overlapped peaks as overlapped. Preserve negative\n   areas as diagnostic evidence of phase\u002Fbaseline problems instead of taking absolute values.\n\n## Execute\n\nTested with Python 3.12, nmrglue 0.12, NumPy 2.5.3, and SciPy 1.18.1:\n\n```bash\nuv run --no-project --python 3.12 --with nmrglue==0.12 --with numpy==2.5.3 --with scipy==1.18.1 \\\n  python skills\u002Fnmrglue\u002Fscripts\u002Fprocess_1d.py fid.npz processing.json nmr-result\n```\n\nPaths assume the collection root. Adjust them when installed elsewhere. The output\ndirectory must be new, so repeated processing keeps previous results reviewable.\n\nFor an existing 1D NMRPipe FID, add `--input-format nmrpipe` and supply its path in place\nof `fid.npz`. The helper requires the canonical FDF2 direct dimension, complex quadrature,\na time-domain flag, and agreement between header and JSON spectral width, observation\nfrequency, and carrier. JSON settings remain explicit; a mismatch fails instead of silently\nrecalibrating. `FDF2TDSIZE` must equal the stored complex-point count, and `FDF2CENTER` \u002F\n`FDF2ORIG` must describe a canonical centered axis. Previously zero-filled, truncated,\nor recentered files need a separate acquisition-aware workflow. The nucleus\u002Fcomplex sign\nand previous digital-filter corrections still need acquisition evidence. A time-domain\nflag alone does not establish an unprocessed FID.\n\nThis executable synthetic example matches the supplied settings, generates resonances\nat 3 and 7 ppm in a 1:2 amplitude ratio, and does not represent an experimental sample:\n\n```python\nimport numpy as np\n\nt = np.arange(8192) \u002F 4000.0\nfid = sum(a * np.exp(-np.pi * 2.0 * t)\n          * np.exp(-2j * np.pi * (ppm - 5.0) * 400.0 * t)\n          for ppm, a in [(3.0, 1.0), (7.0, 2.0)])\nnp.savez(\"fid.npz\", fid=fid)\n```\n\nRun it with `assets\u002Fprocessing.json` as the settings argument. The repository suite\nexecutes this signal and the CLI, checks both peak locations within 0.001 ppm, checks\nintegral ratio and analytic area, and checks phase and baseline recovery. The NMRPipe\nround-trip test writes this FID using `ng.pipe.create_dic`\u002F`ng.pipe.write`, reads it through\nthe CLI, and verifies the recovered peaks and integral ratio. Processed frequency-domain\nfiles and conflicting calibration metadata are rejected.\n\nThe 2,176-byte upstream fixture checks complex sample order and header calibration using\na file generated by NMRPipe's `simTimeND` \u002F `SET` tools. Those native tools were not run\nin this review; this is fixture compatibility, not a live NMRPipe processing comparison.\n\n## Deliverables and interpretation\n\n- `spectrum.csv`: descending ppm, real signal after baseline correction, phased imaginary\n  signal, and the fitted real baseline. Plot NMR with the high-ppm end on the left.\n- `report.json`: input\u002Fsettings SHA-256, package versions, all settings, acquired duration,\n  zero-filled digital spacing, positive peak candidates, and signed region areas.\n\nIntegrals use endpoint interpolation and trapezoidal integration along increasing ppm;\narea units are arbitrary signal times ppm, independent of display direction. Regions\noutside the sampled ppm axis fail rather than being silently clipped. Peak prominence\nis a fraction of the largest positive real intensity; it is not a noise-derived detection\nlimit. Strong solvent signals can obscure weak candidates at the default threshold.\n\nFor quantitative NMR, additionally establish relaxation delay, pulse angle, saturation,\nreceiver behavior, internal\u002Fexternal reference amount, and integration uncertainty.\nThe helper does not calculate concentrations or correct unequal relaxation. Preserve\nthese limits with the result rather than converting arbitrary areas to molecule counts.\n\n## Upstream contracts\n\n- [Processing functions](https:\u002F\u002Fnmrglue.readthedocs.io\u002Fen\u002Flatest\u002Freference\u002Fproc_base.html):\n  exponential apodization, zero filling, FFT, and phase operations.\n- [File and axis utilities](https:\u002F\u002Fnmrglue.readthedocs.io\u002Fen\u002Flatest\u002Freference\u002Ffileiobase.html):\n  unit conversion uses spectral width in Hz, observation frequency in MHz, carrier in Hz.\n- [NMRPipe reader\u002Fwriter](https:\u002F\u002Fnmrglue.readthedocs.io\u002Fen\u002Flatest\u002Freference\u002Fpipe.html):\n  the validated ingestion path is a synthetic canonical 1D time-domain round trip.\n- [nmrglue project](https:\u002F\u002Fgithub.com\u002Fjjhelmus\u002Fnmrglue): upstream source and format readers.\n\nThe hosted `latest` documentation identified itself as 0.9-dev when checked; the actual\n0.12 package APIs and numerical behavior were tested. Its `proc_base.fft` uses the\nnegative-exponent NumPy FFT followed by `fftshift`; NMRPipe's FT convention corresponds\nto `fft_positive`, so do not substitute it without revisiting the FID sign and phase.\nSee the [v0.12 processing source](https:\u002F\u002Fgithub.com\u002Fjjhelmus\u002Fnmrglue\u002Fblob\u002Fv0.12\u002Fnmrglue\u002Fprocess\u002Fproc_base.py).\nMultidimensional processing, nonuniform sampling, automated assignment, and experimental vendor imports remain outside\nthis helper's validated scope.\n","# nmrglue: calibrated 1D FID processing\n\n## When to use\n\nUse for a uniformly sampled complex 1D FID whose acquisition parameters and complex\nfrequency convention are available. The helper produces a descending ppm spectrum,\npositive peak candidates, signed region integrals, and a reproducible processing report.\nIt does not identify compounds or assign resonances.\n\nThe executable accepts a NumPy `.npz` containing exactly one complex `fid` array or a\ncanonical 1D complex time-domain NMRPipe file. NMRPipe reading is tested with a synthetic\nwrite\u002Fread round trip, known-spectrum recovery, and a small upstream NMRPipe-generated\nbinary fixture. Experimental Bruker, Varian, and JEOL\nimports are **not verified by this suite**. For those formats, first inspect the relevant\nnmrglue reader and acquisition metadata. Opening a converted file does not validate the\noriginal acquisition decoding.\nRead [references\u002Facquisition-and-validation.md](references\u002Facquisition-and-validation.md)\nfor conversion boundaries, axis calibration, and quantitative limits.\n\n## Workflow\n\n1. Preserve the raw FID. Establish spectral width in Hz, positive observation frequency\n   in MHz, carrier in ppm, observed nucleus, and the sign convention from the acquisition\n   or a known reference. Determine whether digital-filter\u002Fgroup-delay removal has already\n   occurred. Do not infer these from array length or typical instrument defaults.\n2. Copy [assets\u002Fprocessing.json](assets\u002Fprocessing.json) and replace its synthetic example\n   values with the measured parameters and explicit processing choices. Its sign `-i`\n   means a resonance at offset `f = (ppm - carrier_ppm) * observation_mhz` has time\n   dependence `exp(-2*pi*i*f*t)`. Select `+i` only for the opposite convention; the helper\n   conjugates it before processing. Validate with a known reference peak.\n3. Choose nonnegative exponential line broadening (Hz), an even zero-filled size at\n   least as large as the acquired FID, first-point scaling, and phase angles.\n   Zero filling improves interpolation, not acquired spectral resolution.\n   First-point scaling `0.5` is suitable for the supplied causal synthetic example;\n   acquisition and prior preprocessing may require another value.\n4. Run the helper, inspect the real and imaginary spectra, and revise manual phase if\n   needed. `phase0_deg + phase1_deg * index \u002F zero_fill_points` is applied after FT;\n   index zero is the high-ppm edge. There is no implicit pivot or automatic phase estimate.\n5. Only fit a linear baseline when explicitly supplied ppm regions are signal-free.\n   Set `baseline` to `linear` and add `baseline_regions_ppm` containing at least two\n   regions. Inspect residuals and broad peaks; fitting through signals biases integrals.\n6. Compare peak positions with references, inspect peak candidates for artifacts, and\n   integrate specified regions. Report overlapped peaks as overlapped. Preserve negative\n   areas as diagnostic evidence of phase\u002Fbaseline problems instead of taking absolute values.\n\n## Execute\n\nTested with Python 3.12, nmrglue 0.12, NumPy 2.5.3, and SciPy 1.18.1:\n\n```bash\nuv run --no-project --python 3.12 --with nmrglue==0.12 --with numpy==2.5.3 --with scipy==1.18.1 \\\n  python skills\u002Fnmrglue\u002Fscripts\u002Fprocess_1d.py fid.npz processing.json nmr-result\n```\n\nPaths assume the collection root. Adjust them when installed elsewhere. The output\ndirectory must be new, so repeated processing keeps previous results reviewable.\n\nFor an existing 1D NMRPipe FID, add `--input-format nmrpipe` and supply its path in place\nof `fid.npz`. The helper requires the canonical FDF2 direct dimension, complex quadrature,\na time-domain flag, and agreement between header and JSON spectral width, observation\nfrequency, and carrier. JSON settings remain explicit; a mismatch fails instead of silently\nrecalibrating. `FDF2TDSIZE` must equal the stored complex-point count, and `FDF2CENTER` \u002F\n`FDF2ORIG` must describe a canonical centered axis. Previously zero-filled, truncated,\nor recentered files need a separate acquisition-aware workflow. The nucleus\u002Fcomplex sign\nand previous digital-filter corrections still need acquisition evidence. A time-domain\nflag alone does not establish an unprocessed FID.\n\nThis executable synthetic example matches the supplied settings, generates resonances\nat 3 and 7 ppm in a 1:2 amplitude ratio, and does not represent an experimental sample:\n\n```python\nimport numpy as np\n\nt = np.arange(8192) \u002F 4000.0\nfid = sum(a * np.exp(-np.pi * 2.0 * t)\n          * np.exp(-2j * np.pi * (ppm - 5.0) * 400.0 * t)\n          for ppm, a in [(3.0, 1.0), (7.0, 2.0)])\nnp.savez(\"fid.npz\", fid=fid)\n```\n\nRun it with `assets\u002Fprocessing.json` as the settings argument. The repository suite\nexecutes this signal and the CLI, checks both peak locations within 0.001 ppm, checks\nintegral ratio and analytic area, and checks phase and baseline recovery. The NMRPipe\nround-trip test writes this FID using `ng.pipe.create_dic`\u002F`ng.pipe.write`, reads it through\nthe CLI, and verifies the recovered peaks and integral ratio. Processed frequency-domain\nfiles and conflicting calibration metadata are rejected.\n\nThe 2,176-byte upstream fixture checks complex sample order and header calibration using\na file generated by NMRPipe's `simTimeND` \u002F `SET` tools. Those native tools were not run\nin this review; this is fixture compatibility, not a live NMRPipe processing comparison.\n\n## Deliverables and interpretation\n\n- `spectrum.csv`: descending ppm, real signal after baseline correction, phased imaginary\n  signal, and the fitted real baseline. Plot NMR with the high-ppm end on the left.\n- `report.json`: input\u002Fsettings SHA-256, package versions, all settings, acquired duration,\n  zero-filled digital spacing, positive peak candidates, and signed region areas.\n\nIntegrals use endpoint interpolation and trapezoidal integration along increasing ppm;\narea units are arbitrary signal times ppm, independent of display direction. Regions\noutside the sampled ppm axis fail rather than being silently clipped. Peak prominence\nis a fraction of the largest positive real intensity; it is not a noise-derived detection\nlimit. Strong solvent signals can obscure weak candidates at the default threshold.\n\nFor quantitative NMR, additionally establish relaxation delay, pulse angle, saturation,\nreceiver behavior, internal\u002Fexternal reference amount, and integration uncertainty.\nThe helper does not calculate concentrations or correct unequal relaxation. Preserve\nthese limits with the result rather than converting arbitrary areas to molecule counts.\n\n## Upstream contracts\n\n- [Processing functions](https:\u002F\u002Fnmrglue.readthedocs.io\u002Fen\u002Flatest\u002Freference\u002Fproc_base.html):\n  exponential apodization, zero filling, FFT, and phase operations.\n- [File and axis utilities](https:\u002F\u002Fnmrglue.readthedocs.io\u002Fen\u002Flatest\u002Freference\u002Ffileiobase.html):\n  unit conversion uses spectral width in Hz, observation frequency in MHz, carrier in Hz.\n- [NMRPipe reader\u002Fwriter](https:\u002F\u002Fnmrglue.readthedocs.io\u002Fen\u002Flatest\u002Freference\u002Fpipe.html):\n  the validated ingestion path is a synthetic canonical 1D time-domain round trip.\n- [nmrglue project](https:\u002F\u002Fgithub.com\u002Fjjhelmus\u002Fnmrglue): upstream source and format readers.\n\nThe hosted `latest` documentation identified itself as 0.9-dev when checked; the actual\n0.12 package APIs and numerical behavior were tested. Its `proc_base.fft` uses the\nnegative-exponent NumPy FFT followed by `fftshift`; NMRPipe's FT convention corresponds\nto `fft_positive`, so do not substitute it without revisiting the FID sign and phase.\nSee the [v0.12 processing source](https:\u002F\u002Fgithub.com\u002Fjjhelmus\u002Fnmrglue\u002Fblob\u002Fv0.12\u002Fnmrglue\u002Fprocess\u002Fproc_base.py).\nMultidimensional processing, nonuniform sampling, automated assignment, and experimental vendor imports remain outside\nthis helper's validated scope.\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":29},{"version":25,"skill-author":26,"last-reviewed":27,"tested-package-version":28},"1.1","K-Dense Inc.","2026-10-01","0.12","Requires Python 3.12+, nmrglue, NumPy 2+, and SciPy. Installation needs network access; processing is local and needs no credentials.","master","fd76f882a04e445e899d5cfb2732f2105ea054ee","skills\u002Fawesome-skills\u002Fnmrglue",0,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS","https:\u002F\u002Fbg-szy.github.io\u002FTOP-SKILLS\u002F","https:\u002F\u002Fgithub.com\u002Fbg-szy","https:\u002F\u002Fwww.ecust.edu.cn\u002F","a student of East China University of Science and Technology","2026-11-15 03:38:02",{"source":8,"skillName":5,"commands":41,"prompt":51,"zipAvailable":52},[42,45,48],{"tool":43,"command":44},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill nmrglue",{"tool":46,"command":47},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill nmrglue",{"tool":49,"command":50},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill nmrglue","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fawesome-skills\u002Fnmrglue\u002FSKILL.md",true,[],[55,63,70,77,84,91],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":62},"01M7DXW9N826PKXK174PVW3038","serpmaven","Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fserpmaven\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":62},"01M7DXVHSTWDV65475QEQ915M7","revnu-landing-page-audit","Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: \"audit my landing page\", \"why isn't this page converting\", \"review my homepage\", \"my ads get clicks but no signups\", \"people bounce from the pricing page\", \"CRO review\", \"improve conversion rate\", \"is my hero section clear\", \"roast my landing page\", \"rewrite my headline\", \"what's wrong with this page\", \"landing page feedback\", \"make the signup page convert better\". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-landing-page-audit\u002FSKILL.md",[],[],{"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":76,"publishedAt":62},"01M7DXV8X2D7B3VTD4HHYYHTGR","revnu-growth-context","Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents\u002Frevnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says \"set up our marketing context\", \"who is our ideal customer\", \"write our ICP\", \"describe the product for marketing\", \"positioning doc\", \"what's our brand voice\", \"remember this about our customers\", \"log what we tried\", \"what have we learned from marketing\", \"we changed pricing, update the context\", \"update our growth notes\", \"summarize the business for the agent\", \"import my product-marketing.md\", \"start a growth doc\", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-growth-context\u002FSKILL.md",[],[],{"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":62},"01M7DXV0DGJ1G0A60PAHC6J3C5","revnu-get-listed","Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: \"best X\" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says \"get us listed\", \"which directories should we submit to\", \"how do we get into best-of lists\", \"why does ChatGPT recommend competitors and not us\", \"get mentioned in AI answers\", \"submit to awesome lists\", \"get on G2\", \"where are our competitors listed\", \"pitch listicle authors\", \"find backlink opportunities\", \"launch directories\", \"get into roundups\", \"Product Hunt alternatives\", \"where should we be listed\", \"get cited by Perplexity\". Never submits, pays or posts without a yes. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-get-listed\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":62},"01M7DXTSPMGT9D6DSS0HP9BSTA","revnu-ai-readiness-audit","Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks \"is my site ready for AI search\", \"audit my site for AI answers\", \"AEO audit\", \"GEO audit\", \"why doesn't ChatGPT quote our pricing\", \"make our pages citable by AI\", \"do I need llms.txt\", \"does schema help with ChatGPT\", \"check our structured data\", \"is our content visible without JavaScript\", \"AI SEO audit\", \"optimize our homepage for AI answers\", \"LLM SEO check\", \"why does AI get our product wrong\", \"fix our site for AI Overviews\". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-ai-readiness-audit\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":62},"01M7DXSZHCVTRS620GC3S97JZV","proxy-troubleshooting","Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fproxy-troubleshooting\u002FSKILL.md",[],[]]