[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H6JVYS38FSXAXMWQRRX6GM":3,"skill-same:01M6H6JVYS38FSXAXMWQRRX6GM":82},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M6H6JVYS38FSXAXMWQRRX6GM","markdown-url",null,"Route any website you need to visit through markdown.new by prefixing the URL.\n\n**WHEN TO USE:**\n- You would normally open a website link to read content (docs, blog posts, changelogs, GitHub issues, etc.)\n- You need a cleaner, Markdown-friendly view for copying notes or summarizing","0xharryriddle\u002Fcodex-field-kit","0xharryriddle","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100945007?v=4","01M6H686JV0QKZYP2RWG6B2B8T","harryriddle","01M6H686PVZ8JGKWEG7B3GM5PD",3,"MIT","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Farchive\u002Fupstream\u002Fexamples\u002Fskills\u002Fmarkdown-url\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"markdown","URL","markdown url","use","when to use","for","visit","posts","you","link","route","docs","view","read","blog","open","website","issues","notes","github","2026-11-10 10:12:30",false,"---\nname: markdown-url\ndescription: |\n  Route any website you need to visit through markdown.new by prefixing the URL.\n\n  **WHEN TO USE:**\n  - You would normally open a website link to read content (docs, blog posts, changelogs, GitHub issues, etc.)\n  - You need a cleaner, Markdown-friendly view for copying notes or summarizing\n---\n\n# markdown.new URL Prefix\n\nWhenever you need to visit a website URL, you must:\n1) rewrite it to go through `https:\u002F\u002Fmarkdown.new\u002F`, then\n2) visit the rewritten URL, and\n3) pull the Markdown content from that page for use in your answer\u002Fnotes.\n\n## Rewrite Rule\n\n1. Normalize the destination into an absolute URL with a scheme (`https:\u002F\u002F` preferred).\n2. Prefix it with `https:\u002F\u002Fmarkdown.new\u002F` (do not drop the original scheme).\n\n### Examples\n\n- `https:\u002F\u002Fexample.com` -> `https:\u002F\u002Fmarkdown.new\u002Fhttps:\u002F\u002Fexample.com`\n- `https:\u002F\u002Fexample.com\u002Fdocs?a=1#b` -> `https:\u002F\u002Fmarkdown.new\u002Fhttps:\u002F\u002Fexample.com\u002Fdocs?a=1#b`\n- `example.com` -> `https:\u002F\u002Fmarkdown.new\u002Fhttps:\u002F\u002Fexample.com`\n\n## Agent Workflow (Required)\n\nWhen you would normally open a website to read it:\n\n1. Produce the rewritten `markdown.new` URL.\n2. Visit the rewritten URL first (not the original), but only when it is likely to work (see Policy below).\n3. Extract the page content from the Markdown view (the rendered Markdown and\u002For the raw Markdown).\n4. Use that extracted Markdown as the source for summaries, quotes, checklists, or copy\u002Fpasteable notes.\n\nIf the `markdown.new` view fails to load or breaks critical functionality, fall back to the original URL for browsing, but still prefer `markdown.new` for any content extraction if possible.\n\n## Policy: When To Use markdown.new (Required)\n\nDo NOT route every site through `markdown.new`. Use it primarily for \"read-only\" pages where you want clean, extractable text:\n\n- Documentation pages\n- Blog posts \u002F announcements \u002F changelogs\n- GitHub issues\u002FPR discussions (when you just need readable text)\n- Articles and guides\n\nSkip `markdown.new` and go straight to the original URL when the destination is likely to be blocked or requires the original site behavior:\n\n- Login, OAuth, checkout, payment, or any authenticated workflow\n- Sites that gate content behind JS apps, CAPTCHAs, bot detection, or paywalls\n- File uploads, forms, editors, dashboards, interactive widgets\n- Anything where cookies\u002Fsession state must be preserved\n\n### Block\u002FFailure Signals (Treat As Blocked)\n\nIf you try `markdown.new` and see any of the below, stop retrying and fall back to the original URL:\n\n- HTTP `401\u002F403\u002F429`, \"Access denied\", \"Forbidden\", \"rate limited\"\n- CAPTCHA \u002F \"verify you are human\"\n- Empty\u002Fpartial content that clearly does not match the page\n- Redirect loops or repeated navigation failures\n\n### Fallback Behavior\n\n1. Attempt `markdown.new` once when appropriate.\n2. On block\u002Ffailure, immediately switch to the original URL for browsing.\n3. If you still need extractable text, try to extract from the original page (reader mode \u002F copy text) and clearly note that `markdown.new` was blocked.\n\n## Notes \u002F Exceptions\n\n- Keep this for reading\u002Fbrowsing. For API endpoints, OAuth flows, file uploads, or anything that depends on cookies\u002Flogin state, use the original URL if the proxy breaks functionality.\n- Do not rewrite local paths (`.\u002FREADME.md`) or non-HTTP(S) schemes.\n\n## Optional CLI Helper\n\nConvert a URL into its markdown.new-prefixed form:\n\n```bash\nnode skills\u002Fmarkdown-url\u002Fscripts\u002Fmarkdown-url.js \"https:\u002F\u002Fexample.com\u002Fdocs\"\n```\n","# markdown.new URL Prefix\n\nWhenever you need to visit a website URL, you must:\n1) rewrite it to go through `https:\u002F\u002Fmarkdown.new\u002F`, then\n2) visit the rewritten URL, and\n3) pull the Markdown content from that page for use in your answer\u002Fnotes.\n\n## Rewrite Rule\n\n1. Normalize the destination into an absolute URL with a scheme (`https:\u002F\u002F` preferred).\n2. Prefix it with `https:\u002F\u002Fmarkdown.new\u002F` (do not drop the original scheme).\n\n### Examples\n\n- `https:\u002F\u002Fexample.com` -> `https:\u002F\u002Fmarkdown.new\u002Fhttps:\u002F\u002Fexample.com`\n- `https:\u002F\u002Fexample.com\u002Fdocs?a=1#b` -> `https:\u002F\u002Fmarkdown.new\u002Fhttps:\u002F\u002Fexample.com\u002Fdocs?a=1#b`\n- `example.com` -> `https:\u002F\u002Fmarkdown.new\u002Fhttps:\u002F\u002Fexample.com`\n\n## Agent Workflow (Required)\n\nWhen you would normally open a website to read it:\n\n1. Produce the rewritten `markdown.new` URL.\n2. Visit the rewritten URL first (not the original), but only when it is likely to work (see Policy below).\n3. Extract the page content from the Markdown view (the rendered Markdown and\u002For the raw Markdown).\n4. Use that extracted Markdown as the source for summaries, quotes, checklists, or copy\u002Fpasteable notes.\n\nIf the `markdown.new` view fails to load or breaks critical functionality, fall back to the original URL for browsing, but still prefer `markdown.new` for any content extraction if possible.\n\n## Policy: When To Use markdown.new (Required)\n\nDo NOT route every site through `markdown.new`. Use it primarily for \"read-only\" pages where you want clean, extractable text:\n\n- Documentation pages\n- Blog posts \u002F announcements \u002F changelogs\n- GitHub issues\u002FPR discussions (when you just need readable text)\n- Articles and guides\n\nSkip `markdown.new` and go straight to the original URL when the destination is likely to be blocked or requires the original site behavior:\n\n- Login, OAuth, checkout, payment, or any authenticated workflow\n- Sites that gate content behind JS apps, CAPTCHAs, bot detection, or paywalls\n- File uploads, forms, editors, dashboards, interactive widgets\n- Anything where cookies\u002Fsession state must be preserved\n\n### Block\u002FFailure Signals (Treat As Blocked)\n\nIf you try `markdown.new` and see any of the below, stop retrying and fall back to the original URL:\n\n- HTTP `401\u002F403\u002F429`, \"Access denied\", \"Forbidden\", \"rate limited\"\n- CAPTCHA \u002F \"verify you are human\"\n- Empty\u002Fpartial content that clearly does not match the page\n- Redirect loops or repeated navigation failures\n\n### Fallback Behavior\n\n1. Attempt `markdown.new` once when appropriate.\n2. On block\u002Ffailure, immediately switch to the original URL for browsing.\n3. If you still need extractable text, try to extract from the original page (reader mode \u002F copy text) and clearly note that `markdown.new` was blocked.\n\n## Notes \u002F Exceptions\n\n- Keep this for reading\u002Fbrowsing. For API endpoints, OAuth flows, file uploads, or anything that depends on cookies\u002Flogin state, use the original URL if the proxy breaks functionality.\n- Do not rewrite local paths (`.\u002FREADME.md`) or non-HTTP(S) schemes.\n\n## Optional CLI Helper\n\nConvert a URL into its markdown.new-prefixed form:\n\n```bash\nnode skills\u002Fmarkdown-url\u002Fscripts\u002Fmarkdown-url.js \"https:\u002F\u002Fexample.com\u002Fdocs\"\n```\n",{"name":5,"description":7},"main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","archive\u002Fupstream\u002Fexamples\u002Fskills\u002Fmarkdown-url",0,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit","https:\u002F\u002Fgithub.com\u002F0xharryriddle","https:\u002F\u002Fharryriddle.vercel.app","2026-04-11 11:49:51",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill markdown-url",{"tool":68,"command":69},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill markdown-url",{"tool":71,"command":72},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill markdown-url","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Farchive\u002Fupstream\u002Fexamples\u002Fskills\u002Fmarkdown-url\u002FSKILL.md",true,[76],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002Fmarkdown-url.js","SCRIPT","脚本",785,"https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Farchive\u002Fupstream\u002Fexamples\u002Fskills\u002Fmarkdown-url\u002Fscripts\u002Fmarkdown-url.js",[83,113,131,141,167,189],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":92,"publishedAt":49},"01M6H7ZKE6MR33HC84QZ1TA6MV","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[89],{"categoryNo":90,"categoryName":91,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112],"react best practices","react","vercel react best practices","best practices","vercel","tasks","data fetching","triggers","pages","next","performance optimization","refactoring","Next.js","Optimization","code","guidelines","react components","components","performance","writing",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":49},"01M6H7ZGC2WK8SEKYHWDNTMDA9","swarm-planner","[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fswarm-planner\u002FSKILL.md",[],[120,121,122,123,124,125,126,127,128,34,129,130],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","multi","implementation",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":49},"01M6H7ZD93853RZCYQWH1D38TM","super-swarm-spark","Only to be triggered by explicit super-swarm-spark commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fsuper-swarm-spark\u002FSKILL.md",[],[138,120,139,125,140],"super swarm spark","spark","commands",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":49},"01M6H7Z987QBY49JCCPT953EAZ","role-creator","Create and install Codex custom agent roles in ~\u002F.codex\u002Fconfig.toml, generate role config files, enforce supported keys, and guide users through required role inputs (model, reasoning effort, developer_instructions).","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Frole-creator\u002FSKILL.md",[],[148,149,150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","codex","files",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":176,"publishedAt":49},"01M6H7Z5TRPMDQ7YSZQXPN1G60","read-github","Read and search GitHub repository documentation via gitmcp.io MCP service.\n\n**WHEN TO USE:**\n- User provides a GitHub URL\n- User mentions a specific repo in owner\u002Frepo format\n- User asks \"what does this repo do?\", \"read the docs for X repo\", or similar\n- User wants to search code or docs within a repo","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fread-github\u002FSKILL.md",[173],{"categoryNo":174,"categoryName":175,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[48,177,42,107,178,40,179,180,34,33,30,181,182,183,184,32,185,186,187,188],"read github","documentation","MCP","search","via","io","service","do","user","repo","format","repository",{"skillNo":190,"name":122,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":49},"01M6H7Z215CTKYJ4Y1X6EQWN6M","Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: \"make a plan\", \"create a plan\", \"plan this out\", \"plan the implementation\", \"help me plan\", \"design a plan\", \"draft a plan\", \"write a plan\", \"outline the steps\", \"break this down into tasks\", \"what's the plan for\", or any similar planning request. Also triggers on explicit \"\u002Fplanner\" or \"\u002Fplan\" commands.","https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills\u002Fplanner\u002FSKILL.md",[],[122,195,34,196,197,198,100,127,140,199,200,32,201,202,203,204,205,163,98,206],"outline","atomic","with","sprints","draft","me","write","phased implementation","plan","help","planning","design"]