[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HY3XK64RCS11JCMS9CTJRQ":3,"skill-same:01M6HY3XK64RCS11JCMS9CTJRQ":67},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M6HY3XK64RCS11JCMS9CTJRQ","combined-head-linecount-check",null,"Verify a file's first N lines and total line count in one shell call using head and wc -l with an echo separator, minimizing read operations and shell iterations.","HKUDS\u002FAgentPilot","HKUDS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F118165258?v=4","01M6HW8VRNZP64G0P4MVJW2KKQ","✨Data Intelligence Lab@HKU✨","01M6HW8VWZVHBRHYH3T330PFWV",8029,"MIT","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fshowcase\u002Fskills\u002Fcombined-head-linecount-check\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"check","head","combined head linecount check","file","first","verify","shell","read","operations","Echo","call","line","with","line count","wc","2026-11-10 10:12:30",false,"---\nname: combined-head-linecount-check\ndescription: Verify a file's first N lines and total line count in one shell call using head and wc -l with an echo separator, minimizing read operations and shell iterations.\n---\n\n# Combined Head + Line Count Check\n\nWhen you need to **both** inspect the top of a file and confirm its total line count, collapse the two checks into a single `run_shell` call instead of issuing two separate commands.\n\n## Why\n\n- Each shell call is a round-trip. Two separate calls (`head` then `wc -l`) cost two iterations.\n- A combined call costs one iteration and returns both pieces of information atomically.\n- When checking multiple files at once, each file still only needs one call (or all files can be parallelized in a single compound command).\n\n## Pattern\n\n```bash\nhead -N \u003Cfile> && echo \"---\" && wc -l \u003Cfile>\n```\n\nThe `echo \"---\"` separator makes the output easy to parse visually: everything above the dashes is content, everything below is the line count.\n\n## Examples\n\n### Single file — inspect first 10 lines and total count\n\n```bash\nhead -10 src\u002Fmain.ts && echo \"---\" && wc -l src\u002Fmain.ts\n```\n\nSample output:\n```\nimport { createApp } from 'vue'\nimport App from '.\u002FApp.vue'\n...\n---\n      142 src\u002Fmain.ts\n```\n\n### Multiple files — fully parallelized\n\nWhen you need to check several files simultaneously, run them all in one shell call using `&&` chains or newline-separated subshells:\n\n```bash\n(head -10 src\u002Fmain.ts     && echo \"---\" && wc -l src\u002Fmain.ts)     && echo \"===\" && \\\n(head -10 vite.config.ts  && echo \"---\" && wc -l vite.config.ts)  && echo \"===\" && \\\n(head -5  package.json    && echo \"---\" && wc -l package.json)\n```\n\nOr, if order independence is acceptable, run them in parallel background jobs and wait:\n\n```bash\n{\n  head -10 src\u002Fmain.ts    && echo \"---\" && wc -l src\u002Fmain.ts\n} &\n{\n  head -10 vite.config.ts && echo \"---\" && wc -l vite.config.ts\n} &\nwait\n```\n\n## When to Apply\n\n| Situation | Recommendation |\n|-----------|---------------|\n| Verifying a generated\u002Fmodified file was written correctly | ✅ Use combined call |\n| Checking multiple output files after a build step | ✅ Parallelize all in one shell call |\n| Only need line count (no content preview required) | Use plain `wc -l` |\n| Only need content (no line count required) | Use plain `head -N` |\n| File is extremely large and you want a middle section | Use `sed -n` or `awk` instead |\n\n## Integration with Parallel Reads\n\nThis pattern compounds well with parallel file reads. In a single iteration you can:\n\n1. Read file contents with `cat` or `head` for multiple files.\n2. Simultaneously verify line counts with `wc -l`.\n3. Check for specific patterns with `grep -c`.\n\nExample of a 5-file parallel verification in one shell call:\n\n```bash\necho \"=== main.ts ===\" && head -10 src\u002Fmain.ts && echo \"lines:\" && wc -l \u003C src\u002Fmain.ts && \\\necho \"=== config ===\" && head -5 vite.config.ts && echo \"lines:\" && wc -l \u003C vite.config.ts && \\\necho \"=== package ===\" && head -5 package.json && echo \"lines:\" && wc -l \u003C package.json && \\\necho \"=== index ===\" && head -8 index.html && echo \"lines:\" && wc -l \u003C index.html && \\\necho \"=== readme ===\" && head -5 README.md && echo \"lines:\" && wc -l \u003C README.md\n```\n\n> **Tip:** Using `wc -l \u003C file` (with input redirect) prints only the number, without the filename — cleaner output when the filename is already shown by the `echo` label above it.\n\n## Key Takeaway\n\n> **Never use two shell calls where one will do.** Combining `head -N` and `wc -l` in a single command is the minimal-overhead way to answer both \"what does this file contain?\" and \"is it the right size?\" simultaneously.","# Combined Head + Line Count Check\n\nWhen you need to **both** inspect the top of a file and confirm its total line count, collapse the two checks into a single `run_shell` call instead of issuing two separate commands.\n\n## Why\n\n- Each shell call is a round-trip. Two separate calls (`head` then `wc -l`) cost two iterations.\n- A combined call costs one iteration and returns both pieces of information atomically.\n- When checking multiple files at once, each file still only needs one call (or all files can be parallelized in a single compound command).\n\n## Pattern\n\n```bash\nhead -N \u003Cfile> && echo \"---\" && wc -l \u003Cfile>\n```\n\nThe `echo \"---\"` separator makes the output easy to parse visually: everything above the dashes is content, everything below is the line count.\n\n## Examples\n\n### Single file — inspect first 10 lines and total count\n\n```bash\nhead -10 src\u002Fmain.ts && echo \"---\" && wc -l src\u002Fmain.ts\n```\n\nSample output:\n```\nimport { createApp } from 'vue'\nimport App from '.\u002FApp.vue'\n...\n---\n      142 src\u002Fmain.ts\n```\n\n### Multiple files — fully parallelized\n\nWhen you need to check several files simultaneously, run them all in one shell call using `&&` chains or newline-separated subshells:\n\n```bash\n(head -10 src\u002Fmain.ts     && echo \"---\" && wc -l src\u002Fmain.ts)     && echo \"===\" && \\\n(head -10 vite.config.ts  && echo \"---\" && wc -l vite.config.ts)  && echo \"===\" && \\\n(head -5  package.json    && echo \"---\" && wc -l package.json)\n```\n\nOr, if order independence is acceptable, run them in parallel background jobs and wait:\n\n```bash\n{\n  head -10 src\u002Fmain.ts    && echo \"---\" && wc -l src\u002Fmain.ts\n} &\n{\n  head -10 vite.config.ts && echo \"---\" && wc -l vite.config.ts\n} &\nwait\n```\n\n## When to Apply\n\n| Situation | Recommendation |\n|-----------|---------------|\n| Verifying a generated\u002Fmodified file was written correctly | ✅ Use combined call |\n| Checking multiple output files after a build step | ✅ Parallelize all in one shell call |\n| Only need line count (no content preview required) | Use plain `wc -l` |\n| Only need content (no line count required) | Use plain `head -N` |\n| File is extremely large and you want a middle section | Use `sed -n` or `awk` instead |\n\n## Integration with Parallel Reads\n\nThis pattern compounds well with parallel file reads. In a single iteration you can:\n\n1. Read file contents with `cat` or `head` for multiple files.\n2. Simultaneously verify line counts with `wc -l`.\n3. Check for specific patterns with `grep -c`.\n\nExample of a 5-file parallel verification in one shell call:\n\n```bash\necho \"=== main.ts ===\" && head -10 src\u002Fmain.ts && echo \"lines:\" && wc -l \u003C src\u002Fmain.ts && \\\necho \"=== config ===\" && head -5 vite.config.ts && echo \"lines:\" && wc -l \u003C vite.config.ts && \\\necho \"=== package ===\" && head -5 package.json && echo \"lines:\" && wc -l \u003C package.json && \\\necho \"=== index ===\" && head -8 index.html && echo \"lines:\" && wc -l \u003C index.html && \\\necho \"=== readme ===\" && head -5 README.md && echo \"lines:\" && wc -l \u003C README.md\n```\n\n> **Tip:** Using `wc -l \u003C file` (with input redirect) prints only the number, without the filename — cleaner output when the filename is already shown by the `echo` label above it.\n\n## Key Takeaway\n\n> **Never use two shell calls where one will do.** Combining `head -N` and `wc -l` in a single command is the minimal-overhead way to answer both \"what does this file contain?\" and \"is it the right size?\" simultaneously.",{"name":5,"description":7},"main","6b84b0689ca0d9e7b1e4061188ff6b60758e0f8a","openspace\u002Flegacy\u002Fv1\u002Fshowcase\u002Fskills\u002Fcombined-head-linecount-check",944,"https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot","https:\u002F\u002Fgithub.com\u002FHKUDS","https:\u002F\u002Fsites.google.com\u002Fview\u002Fchaoh","2026-11-12 22:26:39",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add HKUDS\u002FAgentPilot --skill combined-head-linecount-check",{"tool":53,"command":54},"bunx","bunx skills add HKUDS\u002FAgentPilot --skill combined-head-linecount-check",{"tool":56,"command":57},"pnpm","pnpm dlx skills add HKUDS\u002FAgentPilot --skill combined-head-linecount-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fshowcase\u002Fskills\u002Fcombined-head-linecount-check\u002FSKILL.md",true,[61],{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},".skill_id","OTHER","其他",43,"https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fshowcase\u002Fskills\u002Fcombined-head-linecount-check\u002F.skill_id",[68,87,106,131,155,176],{"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":34},"01M6HYB297NDABRERJRVG0K8R0","agentpilot","Set up AgentPilot and use its single entry to prepare missing inputs and run configured RSI experiments. Use when the user requests AgentPilot installation or work with AgentPilot.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fplugins\u002Fagentpilot\u002Fskills\u002Fagentpilot\u002FSKILL.md",[],[70,75,76,31,77,78,79,80,81,82,83,84,85,86],"prepare","requests","missing","installation","rsi","up","use","user","work","SET","run","experiments",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":34},"01M6HYAYWXTTE1J7DJM0MFNQ4H","remember","Review auto-memory entries and propose promotions to OPENSPACE.md, OPENSPACE.local.md, or retained auto-memory topics; detect duplicates, stale facts, conflicts, and ambiguous entries before making changes.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fopenspace\u002Fskills\u002Fremember\u002FSKILL.md",[],[89,94,95,96,97,98,99,100,101,102,103,104,105],"memory","review","auto","openspace","changes","facts","detect","entries","local","conflicts","stale","duplicates",{"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":117,"publishedAt":34},"01M6HYAVMPM4SBDV60R2B5HPV8","skill-discovery","Search reusable OpenSpace skills locally, and browse cloud packages step by step when a cloud skill may help. Reusing proven skills saves tokens, improves reliability, and extends your capabilities beyond built-in tools.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fopenspace\u002Fhost_skills\u002Fskill-discovery\u002FSKILL.md",[112],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[118,119,120,97,121,122,123,124,125,126,127,128,129,130],"skill discovery","discovery","reusable","step by step","tokens","packages","help","cloud","reliability","capabilities","browse","search","Tools",{"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":138,"publishedAt":34},"01M6HYAR811B3RB0M50RBEDGN6","delegate-task","Delegate tasks to OpenSpace — a full-stack autonomous worker for coding, DevOps, web research, and desktop automation, backed by an extensive MCP tool and skill library. Skills auto-improve through use, reducing token consumption over time. A cloud community lets agents share and collectively evolve reusable skills.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Fopenspace\u002Fhost_skills\u002Fdelegate-task\u002FSKILL.md",[137],{"categoryNo":113,"categoryName":114,"taxonomyType":115,"taxonomyTypeDesc":116},[139,140,141,97,142,143,144,145,146,120,96,81,147,148,149,150,151,152,153,154],"delegate","task","delegate task","time","improve","desktop automation","worker","community","autonomous","tool","stack","for","share","tasks","automation","MCP",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":161,"publishedAt":34},"01M6HYAM9FSGV6E52AYENDQXYH","write-special-chars-ts-check","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[162,163,19,164,165,166,167,168,22,169,170,171,172,173,150,174,175],"write special chars ts check","write","type","files","filters","only","template","python","typescript","output","Existing","type-checking","errors","script",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":34},"01M6HYAH05HGV7SVWSVR8PJRQD","write-special-chars-readback","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of \u002Ftmp helper scripts.","https:\u002F\u002Fgithub.com\u002FHKUDS\u002FAgentPilot\u002Fblob\u002Fmain\u002Fopenspace\u002Flegacy\u002Fv1\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[183,184,163,31,150,175,185,186,187,188,26,168,22,189,190,169],"write special chars readback","readback","helper","post","via","scripts","verification","cleanup"]