[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6EKHBJ8ZYV9E11T2RE35X4D":3,"skill-same:01M6EKHBJ8ZYV9E11T2RE35X4D":64},{"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":23,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6EKHBJ8ZYV9E11T2RE35X4D","benchpress-docs",null,"Read and search the BenchPress documentation. Use when working with BenchPress — its setup, configuration, API, and behavior.","Venkateshvenki404224\u002Fbenchpress","Venkateshvenki404224","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75518037?v=4","01M6EKFVM5P6HRTJBSR8BABRJ2","Venkatesh","01M6EKFVRVS346Q492S7SASWTV",6,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002FVenkateshvenki404224\u002Fbenchpress\u002Fblob\u002Fversion-16\u002Fdocs-site\u002F.well-known\u002Fagent-skills\u002Fbenchpress-docs\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33],"docs","benchpress docs","setup","documentation","search","api","read","behavior","use","configuration","2026-11-10 10:12:30",false,"---\nname: benchpress-docs\ndescription: Read and search the BenchPress documentation. Use when working with BenchPress — its setup, configuration, API, and behavior.\nmetadata:\n  source: leadtype\n---\n# BenchPress documentation\n\nPress a button. Get a Frappe bench.\n\nTo work with BenchPress, read its documentation:\n\n- Start at `\u002Fllms.txt` (task-routed index) or `\u002Fllms-full.txt` (full context).\n- Every page is also available as Markdown at its `.md` URL.\n","# BenchPress documentation\n\nPress a button. Get a Frappe bench.\n\nTo work with BenchPress, read its documentation:\n\n- Start at `\u002Fllms.txt` (task-routed index) or `\u002Fllms-full.txt` (full context).\n- Every page is also available as Markdown at its `.md` URL.\n",{"name":5,"metadata":39,"description":7},{"source":40},"leadtype","version-16","38e17b09d0a500b359ccf7abf4cc0557dcd605e4","docs-site\u002F.well-known\u002Fagent-skills\u002Fbenchpress-docs",1,"https:\u002F\u002Fgithub.com\u002FVenkateshvenki404224\u002Fbenchpress","https:\u002F\u002Fbenchpress.cloud","https:\u002F\u002Fgithub.com\u002FVenkateshvenki404224","🚀 Backend Engineer | 🧠 Open Source Contributor | ⚙️ Frappe & ERPNext Expert | 🔬 Lab Infra Builder | 👕 Founder @gemzy.in | 💡 Building Dev Tools","2026-11-09 02:43:13",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add Venkateshvenki404224\u002Fbenchpress --skill benchpress-docs",{"tool":56,"command":57},"bunx","bunx skills add Venkateshvenki404224\u002Fbenchpress --skill benchpress-docs",{"tool":59,"command":60},"pnpm","pnpm dlx skills add Venkateshvenki404224\u002Fbenchpress --skill benchpress-docs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FVenkateshvenki404224\u002Fbenchpress\u002Fblob\u002Fversion-16\u002Fdocs-site\u002F.well-known\u002Fagent-skills\u002Fbenchpress-docs\u002FSKILL.md",true,[],[65,77,106,139,157,187],{"skillNo":66,"name":5,"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":76,"publishedAt":34},"01M6EKH56APEWPT12654C9HG67","Read and search the benchpress documentation. Use when working with benchpress — its setup, configuration, API, and behavior.","https:\u002F\u002Fgithub.com\u002FVenkateshvenki404224\u002Fbenchpress\u002Fblob\u002Fversion-16\u002Fdocs-bundle\u002FSKILL.md",[70,75],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,25,26,27,28,29,30,31,32,33],{"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":89,"publishedAt":34},"01M6EKH20VPHEBRS67AMARTJRV","ui-design","General UI\u002FUX judgment for layout, polish, visual hierarchy, spacing, typography, color, and accessibility. Use when no product-specific or Frappe-specific design system skill applies.","https:\u002F\u002Fgithub.com\u002FVenkateshvenki404224\u002Fbenchpress\u002Fblob\u002Fversion-16\u002F.claude\u002Fskills\u002Fui-design\u002FSKILL.md",[83,86],{"categoryNo":84,"categoryName":85,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":87,"categoryName":88,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[90,91,92,93,94,95,96,97,98,32,99,100,101,102,103,104,105],"design","ui","ui design","accessibility","design system","product","ux","polish","system","typography","general","visual","judgment","layout","color","frappe",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":119,"publishedAt":34},"01M6EKGYTRTQHD402K7BBJG669","technical-writing","Write prose in \"Simplified Technical English\". This applies to documentation, READMEs, commits, pull request, plans and release notes. It does not apply to code, identifiers, marketing copy, essays, or anything that needs a voice.","https:\u002F\u002Fgithub.com\u002FVenkateshvenki404224\u002Fbenchpress\u002Fblob\u002Fversion-16\u002F.claude\u002Fskills\u002Ftechnical-writing\u002FSKILL.md",[112,115,116],{"categoryNo":113,"categoryName":114,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[120,121,122,27,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138],"writing","technical writing","technical","notes","pull request","release notes","code","release","pull","commits","marketing","voice","write","prose","plans","english","simplified technical english","copy","it",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":34},"01M6EKGVVJHPXAR0PC0R8SS8Y8","resolve-backport-conflicts","Resolve merge conflicts in a Mergify backport pull request. When a cherry-pick fails, Mergify commits the conflict markers as they are. This skill takes a pull request link or number as an argument.","https:\u002F\u002Fgithub.com\u002FVenkateshvenki404224\u002Fbenchpress\u002Fblob\u002Fversion-16\u002F.claude\u002Fskills\u002Fresolve-backport-conflicts\u002FSKILL.md",[],[146,147,148,149,124,128,150,129,151,152,153,154,155,156],"backport","conflicts","resolve backport conflicts","merge","resolve merge conflicts","pick","merge conflicts","conflict","as","link","markers",{"skillNo":158,"name":159,"nameZh":6,"description":160,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":161,"categories":162,"keywords":171,"publishedAt":34},"01M6EKGRAG062FCM7SA3303GWQ","quality-code-review","Review code for any Frappe application — a checklist distilled from years of engineering practice on correctness, security, performance, concurrency, readability, API design, and testing. Use this when reviewing a diff, a PR, or a piece of code for quality and security, or when you want a reviewer's checklist grounded in hard-won Frappe\u002FERPNext lessons.","https:\u002F\u002Fgithub.com\u002FVenkateshvenki404224\u002Fbenchpress\u002Fblob\u002Fversion-16\u002F.claude\u002Fskills\u002Fquality-code-review\u002FSKILL.md",[163,166,169,170],{"categoryNo":164,"categoryName":165,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":167,"categoryName":168,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":84,"categoryName":85,"taxonomyType":73,"taxonomyTypeDesc":74},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[172,173,126,174,175,176,177,90,178,179,180,181,29,182,183,32,184,185,186,105],"code review","review","quality","quality code","quality code review","testing","security","performance","pr","concurrency","review code","reviewer","diff","readability","erpnext",{"skillNo":188,"name":189,"nameZh":6,"description":190,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":191,"categories":192,"keywords":196,"publishedAt":34},"01M6EKGKNGNVHYJHZZ456N4DVW","issue-to-phases","Decompose a planning document (plan.md, a spec, or a GitHub issue) into incremental, independently-shippable \"tracer bullet\" phases, write them as phase specs under specs\u002F, and optionally generate a Ralph loop (ralph.sh + prompt.md) that implements them unattended. Use this whenever the user hands you a plan and wants it broken into phases, mentions \"tracer bullets\", \"phase 0\u002F1\u002F2\", \"build this in phases\", \"thin end-to-end slice first\", \"ralph loop\", or wants phased specs in the specs\u002F folder — even if they never say the word \"phase\". Also use it when the user asks to \"implement \u002F work on phase N\" of an existing spec folder, so the branch, the PR and the spec's status all move the way every earlier phase did.","https:\u002F\u002Fgithub.com\u002FVenkateshvenki404224\u002Fbenchpress\u002Fblob\u002Fversion-16\u002F.claude\u002Fskills\u002Fissue-to-phases\u002FSKILL.md",[193],{"categoryNo":194,"categoryName":195,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000002","文档处理",[197,198,199,180,200,201,202,203,204,205,206,207,208,209,132,32,210,211,212,154],"issue","issue to phases","status","generate","planning","loop","plan","work on","Word","ralph","work","branch","broken","never","decompose","end"]