[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76GK3WHV1YAWJ684ST693K6":3,"skill-same:01M76GK3WHV1YAWJ684ST693K6":59},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M76GK3WHV1YAWJ684ST693K6","deloreis",null,"Keep fiction and worldbuilding consistent with De Lore Is. Use when maintaining lore for AI-assisted novels, series bibles, campaigns, competing story ideas, retcons, or checks on generated additions to a fictional world. Record and query persistent lore through local MCP tools. Also use for explicit De Lore Is, DLI, or deloreis project requests.","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\u002Fmarketplace\u002Fdeloreis\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fdeloreis\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: deloreis\ndescription: Keep fiction and worldbuilding consistent with De Lore Is. Use when maintaining lore for AI-assisted novels, series bibles, campaigns, competing story ideas, retcons, or checks on generated additions to a fictional world. Record and query persistent lore through local MCP tools. Also use for explicit De Lore Is, DLI, or deloreis project requests.\nlicense: MIT\n---\n\n# Authoring with De Lore Is\n\nUse De Lore Is when a writing task needs an established world to check against:\ncontinuing a novel, adding lore, revising an account, or exploring another version\nof a story. It records structured lore and checks the rules supplied for that\nworld. Keep the manuscript and prose references in their existing files.\n\nFor installation and a complete first check, read\n[First session](references\u002Ffirst-session.md). The skill does not install the\nruntime. Start with a small section of the user's notes, not a whole-book\nmigration. Ask which details are established and which are ideas. Propose rules\ninstead of assuming, for example, that every character can have only one home.\n\nUse the `author.*` tools to add lore. Read every returned finding. Repair\nmechanical input errors; resolve continuity findings using the user's rulings\nrather than change lore just to make a check pass. Do not edit `.dli` as an agent\nauthoring a world. People can write `.dli` directly and import or check it;\nthe store is the source of truth for an authoring session.\n\nRegister `deloreis mcp --project \u003Cdirectory>` with the client, then call its\ntools. If they are not available, use the first-session setup instead of\nsimulating a stored world in the chat. The server\nalso offers newline-delimited JSON through `deloreis serve --project\n\u003Cdirectory>`. Contract 2.0.0 is the served contract. `--tools all` advertises\nspecialist tools beyond the default profile. Use installed help and `tools\u002Flist`\nfor the exact arguments rather than guessing tool schemas.\n\n## Authoring loop\n\n1. `author.open` a scope and retain its returned workspace ID and digest.\n   When fencing writes, pass the current digest as `expected_digest`; read the\n   updated `workspace_digest` from the result or `author.status` after each\n   change rather than reuse an earlier one.\n2. Use typed operations such as `author.add_entity`, `author.add_fact`,\n   `author.add_relation`, `author.add_event`, and `author.add_before`.\n   Declare single-valued predicates with `author.declare_functional` and\n   changing predicates with `author.declare_inertial` where appropriate.\n3. Check the project's source\u002Fdecision index before choosing a new decision ID;\n   reuse an ID only for that same ruling. For a ruling, use `author.record_decision` and cite that decision with\n   `{\"kind\":\"cited\",\"decisions\":[\"d-0001\"],\"state\":\"ratified\"}`. An\n   unruled proposal can use `{\"kind\":\"proposed\",\"origin\":\"session-name\"}`.\n   Unknown citations are errors and cannot make a claim certain.\n4. Inspect `author.check`, `author.findings`, `author.query`, and `author.why`.\n   `author.diff` shows staged consequences. Check the returned findings even\n   if the call itself succeeded.\n5. `author.materialize` checks and commits staged changes. It refuses errors.\n   `author.discard` rejects staged work. Keep returned root hashes and claim\n   IDs when they are useful for review or later retcons.\n\n`author.record_decision`, `author.defeat`, and standing operations can update\nthe store directly; do not assume that every mutation is only staged. Use the\nuser's agreed rulings and the host's review policy before these calls; do not\nsilently turn an idea into an accepted account. The\ncaller supplies attribution, decision state, and review policy. The server\nchecks references and continuity, not who is authorized to rule.\n\n## Use it during a writing task\n\n- **Continue a chapter:** query the people, places, and established facts relevant\n  to the scene. After drafting, propose the new factual claims through the tools,\n  check them, and show the user any conflicts. Review extracted claims against\n  the prose; a clean check covers those claims and recorded rules.\n- **Brainstorm:** keep alternatives proposed or in a hypothetical fork. Use\n  `author.open_question` and `author.add_option` for a choice between accounts;\n  `author.add_hypothesis` and `author.suppose` support hypothetical exploration. Accepting\n  a note into the store does not by itself make it established canon. Query\n  established claims with `layer: \"certain\"`. Use `layer: \"possible\"` or `\"all\"`\n  to inspect open accounts as well; those layers also include certain claims.\n  A known claim can evaluate dead, but there is no `dead` query layer: inspect\n  its blocked support with `author.why`.\n- **Revise:** inspect `author.diff` and `author.why`, then record the user's chosen\n  new ruling before calling `author.defeat` on the earlier support. Retain the old claim ID. Use a named\n  branch for a separate durable version; branch tools are advertised with `--tools all`.\n- **Track change within the story:** record event-anchored states and query\n  `author.as_of`. A character changing allegiance is not necessarily a retcon.\n  Declare known event ordering; leave unknown ordering open.\n\nNew workspaces see current committed lore; an already-open workspace retains its\nbase. Open a fresh workspace when another session has changed the accepted\nworld. The host application owns approval, access control, and concurrent-write\npolicy. Do not describe DLI as general-purpose agent memory or infer a character's\nknowledge from world facts.\n\nFor CLI reads and wiki export, see [Read and export](references\u002Ffirst-session.md#read-and-export).\n\n## Core tools\n\nThe default MCP profile keeps 29 common tools. It advertises `dli.check`, `dli.name.check`, and:\n\n- Workspace and inspection: `author.open`, `author.status`, `author.check`,\n  `author.findings`, `author.predicates`, `author.query`, `author.why`,\n  `author.as_of`, `author.diff`, and `author.entity_candidates`.\n- Lore: `author.add_entity`, `author.add_fact`, `author.add_relation`,\n  `author.add_event`, `author.add_before`, `author.add_state`,\n  `author.declare_functional`, and `author.declare_inertial`.\n- Rulings and exploration: `author.record_decision`, `author.open_question`,\n  `author.add_option`, `author.defeat`, `author.set_standing`,\n  `author.add_hypothesis`, and `author.suppose`.\n- Acceptance: `author.materialize` and `author.discard`.\n\n`author.add_option` can name a fact that follows if that option is chosen,\nusing its optional `implies` field. Give options distinct names and add them\nbefore materializing their question.\n\nUse `tools\u002Flist` for the exact schemas. `author.query` returns claim IDs when\navailable; `author.why` explains supporting and blocked paths. For a retcon,\n`author.defeat` takes a claim ID, a new decision, and the decision it defeats.\nDefeating the retcon can restore the original support. Use `--tools all` for\nnamed branches, specialist authoring, corpus import\u002Fexport, and other tools.\n\nThe [Holmes casebook](https:\u002F\u002Fjeffreykentjr.github.io\u002Fdeloreis\u002Fcasebook-01.html) is produced from a\nreplay that exercises the server. The [concept glossary](https:\u002F\u002Fjeffreykentjr.github.io\u002Fdeloreis\u002Fconcepts.html) explains\nthe terms. DLI checks structured claims, not prose, and a functional conflict\nis detected only for a predicate declared single-valued.\n\n## Reading rendered lore\n\nThese are supported readable `.dli` forms. Agents author through the tools\ninstead of editing these snippets into the project:\n\n```dli\nperson wren \"Wren\" proposed session\n```\n\n```dli\nfunctional home proposed session\n```\n\n```dli\nhome(wren, thornfield) ratified d-0001\n```\n","# Authoring with De Lore Is\n\nUse De Lore Is when a writing task needs an established world to check against:\ncontinuing a novel, adding lore, revising an account, or exploring another version\nof a story. It records structured lore and checks the rules supplied for that\nworld. Keep the manuscript and prose references in their existing files.\n\nFor installation and a complete first check, read\n[First session](references\u002Ffirst-session.md). The skill does not install the\nruntime. Start with a small section of the user's notes, not a whole-book\nmigration. Ask which details are established and which are ideas. Propose rules\ninstead of assuming, for example, that every character can have only one home.\n\nUse the `author.*` tools to add lore. Read every returned finding. Repair\nmechanical input errors; resolve continuity findings using the user's rulings\nrather than change lore just to make a check pass. Do not edit `.dli` as an agent\nauthoring a world. People can write `.dli` directly and import or check it;\nthe store is the source of truth for an authoring session.\n\nRegister `deloreis mcp --project \u003Cdirectory>` with the client, then call its\ntools. If they are not available, use the first-session setup instead of\nsimulating a stored world in the chat. The server\nalso offers newline-delimited JSON through `deloreis serve --project\n\u003Cdirectory>`. Contract 2.0.0 is the served contract. `--tools all` advertises\nspecialist tools beyond the default profile. Use installed help and `tools\u002Flist`\nfor the exact arguments rather than guessing tool schemas.\n\n## Authoring loop\n\n1. `author.open` a scope and retain its returned workspace ID and digest.\n   When fencing writes, pass the current digest as `expected_digest`; read the\n   updated `workspace_digest` from the result or `author.status` after each\n   change rather than reuse an earlier one.\n2. Use typed operations such as `author.add_entity`, `author.add_fact`,\n   `author.add_relation`, `author.add_event`, and `author.add_before`.\n   Declare single-valued predicates with `author.declare_functional` and\n   changing predicates with `author.declare_inertial` where appropriate.\n3. Check the project's source\u002Fdecision index before choosing a new decision ID;\n   reuse an ID only for that same ruling. For a ruling, use `author.record_decision` and cite that decision with\n   `{\"kind\":\"cited\",\"decisions\":[\"d-0001\"],\"state\":\"ratified\"}`. An\n   unruled proposal can use `{\"kind\":\"proposed\",\"origin\":\"session-name\"}`.\n   Unknown citations are errors and cannot make a claim certain.\n4. Inspect `author.check`, `author.findings`, `author.query`, and `author.why`.\n   `author.diff` shows staged consequences. Check the returned findings even\n   if the call itself succeeded.\n5. `author.materialize` checks and commits staged changes. It refuses errors.\n   `author.discard` rejects staged work. Keep returned root hashes and claim\n   IDs when they are useful for review or later retcons.\n\n`author.record_decision`, `author.defeat`, and standing operations can update\nthe store directly; do not assume that every mutation is only staged. Use the\nuser's agreed rulings and the host's review policy before these calls; do not\nsilently turn an idea into an accepted account. The\ncaller supplies attribution, decision state, and review policy. The server\nchecks references and continuity, not who is authorized to rule.\n\n## Use it during a writing task\n\n- **Continue a chapter:** query the people, places, and established facts relevant\n  to the scene. After drafting, propose the new factual claims through the tools,\n  check them, and show the user any conflicts. Review extracted claims against\n  the prose; a clean check covers those claims and recorded rules.\n- **Brainstorm:** keep alternatives proposed or in a hypothetical fork. Use\n  `author.open_question` and `author.add_option` for a choice between accounts;\n  `author.add_hypothesis` and `author.suppose` support hypothetical exploration. Accepting\n  a note into the store does not by itself make it established canon. Query\n  established claims with `layer: \"certain\"`. Use `layer: \"possible\"` or `\"all\"`\n  to inspect open accounts as well; those layers also include certain claims.\n  A known claim can evaluate dead, but there is no `dead` query layer: inspect\n  its blocked support with `author.why`.\n- **Revise:** inspect `author.diff` and `author.why`, then record the user's chosen\n  new ruling before calling `author.defeat` on the earlier support. Retain the old claim ID. Use a named\n  branch for a separate durable version; branch tools are advertised with `--tools all`.\n- **Track change within the story:** record event-anchored states and query\n  `author.as_of`. A character changing allegiance is not necessarily a retcon.\n  Declare known event ordering; leave unknown ordering open.\n\nNew workspaces see current committed lore; an already-open workspace retains its\nbase. Open a fresh workspace when another session has changed the accepted\nworld. The host application owns approval, access control, and concurrent-write\npolicy. Do not describe DLI as general-purpose agent memory or infer a character's\nknowledge from world facts.\n\nFor CLI reads and wiki export, see [Read and export](references\u002Ffirst-session.md#read-and-export).\n\n## Core tools\n\nThe default MCP profile keeps 29 common tools. It advertises `dli.check`, `dli.name.check`, and:\n\n- Workspace and inspection: `author.open`, `author.status`, `author.check`,\n  `author.findings`, `author.predicates`, `author.query`, `author.why`,\n  `author.as_of`, `author.diff`, and `author.entity_candidates`.\n- Lore: `author.add_entity`, `author.add_fact`, `author.add_relation`,\n  `author.add_event`, `author.add_before`, `author.add_state`,\n  `author.declare_functional`, and `author.declare_inertial`.\n- Rulings and exploration: `author.record_decision`, `author.open_question`,\n  `author.add_option`, `author.defeat`, `author.set_standing`,\n  `author.add_hypothesis`, and `author.suppose`.\n- Acceptance: `author.materialize` and `author.discard`.\n\n`author.add_option` can name a fact that follows if that option is chosen,\nusing its optional `implies` field. Give options distinct names and add them\nbefore materializing their question.\n\nUse `tools\u002Flist` for the exact schemas. `author.query` returns claim IDs when\navailable; `author.why` explains supporting and blocked paths. For a retcon,\n`author.defeat` takes a claim ID, a new decision, and the decision it defeats.\nDefeating the retcon can restore the original support. Use `--tools all` for\nnamed branches, specialist authoring, corpus import\u002Fexport, and other tools.\n\nThe [Holmes casebook](https:\u002F\u002Fjeffreykentjr.github.io\u002Fdeloreis\u002Fcasebook-01.html) is produced from a\nreplay that exercises the server. The [concept glossary](https:\u002F\u002Fjeffreykentjr.github.io\u002Fdeloreis\u002Fconcepts.html) explains\nthe terms. DLI checks structured claims, not prose, and a functional conflict\nis detected only for a predicate declared single-valued.\n\n## Reading rendered lore\n\nThese are supported readable `.dli` forms. Agents author through the tools\ninstead of editing these snippets into the project:\n\n```dli\nperson wren \"Wren\" proposed session\n```\n\n```dli\nfunctional home proposed session\n```\n\n```dli\nhome(wren, thornfield) ratified d-0001\n```\n",{"name":5,"license":15,"description":7},"master","fd76f882a04e445e899d5cfb2732f2105ea054ee","skills\u002Fmarketplace\u002Fdeloreis",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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill deloreis",{"tool":41,"command":42},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill deloreis",{"tool":44,"command":45},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill deloreis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fdeloreis\u002FSKILL.md",true,[49,53],{"path":50,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":16},"LICENSE","许可证",1069,{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"skill-report.json","REFERENCE","参考文档",57766,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fdeloreis\u002Fskill-report.json",[60,68,75,82,89,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":67},"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":67},"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":67},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":67},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":67},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":67},"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",[],[]]