[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H6QWGCHC5CASR2T0SJ22QE":3,"skill-same:01M6H6QWGCHC5CASR2T0SJ22QE":63},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M6H6QWGCHC5CASR2T0SJ22QE","bash-expert",null,"Use when implementing bash functionality with production-grade patterns and safeguards.","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\u002Fskills-hermes\u002Fcodex-agents\u002Fbash-expert\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29],"Bash","expert","bash expert","codex","Production","use","patterns","runtime","with","kit","implementing","2026-11-10 10:12:30",false,"---\nname: bash-expert\ndescription: Use when implementing bash functionality with production-grade patterns and safeguards.\nmetadata:\n  hermes:\n    tags: [codex-agent, languages-runtime]\n    source: codex-field-kit\u002Flanguages-runtime\n---\n\n# Bash Expert\n\n## Focus Areas\n\n- Defensive programming with strict error handling\n- POSIX compliance and cross-platform portability\n- Safe argument parsing and input validation\n- Robust file operations and temporary resource management\n- Process orchestration and pipeline safety\n- Production-grade logging and error reporting\n- Comprehensive testing with Bats framework\n- Static analysis with ShellCheck and formatting with shfmt\n- Modern Bash 5.x features and best practices\n- CI\u002FCD integration and automation workflows\n\n## Approach\n\n- Always use strict mode with `set -Eeuo pipefail` and proper error trapping\n- Quote all variable expansions to prevent word splitting and globbing issues\n- Prefer arrays and proper iteration over unsafe patterns like `for f in $(ls)`\n- Use `[[ ]]` for Bash conditionals, fall back to `[ ]` for POSIX compliance\n- Implement comprehensive argument parsing with `getopts` and usage functions\n- Create temporary files and directories safely with `mktemp` and cleanup traps\n- Prefer `printf` over `echo` for predictable output formatting\n- Use command substitution `$()` instead of backticks for readability\n- Implement structured logging with timestamps and configurable verbosity\n- Design scripts to be idempotent and support dry-run modes\n- Use `shopt -s inherit_errexit` for better error propagation in Bash 4.4+\n- Employ `IFS=$'\\n\\t'` to prevent unwanted word splitting on spaces\n- Validate inputs with `: \"${VAR:?message}\"` for required environment variables\n- End option parsing with `--` and use `rm -rf -- \"$dir\"` for safe operations\n- Support `--trace` mode with `set -x` opt-in for detailed debugging\n- Use `xargs -0` with NUL boundaries for safe subprocess orchestration\n- Employ `readarray`\u002F`mapfile` for safe array population from command output\n- Implement robust script directory detection: `SCRIPT_DIR=\"$(cd -- \"$(dirname -- \"${BASH_SOURCE[0]}\")\" && pwd -P)\"`\n- Use NUL-safe patterns: `find -print0 | while IFS= read -r -d '' file; do ...; done`\n\n## Quality Checklist\n\n- Scripts pass ShellCheck static analysis with minimal suppressions\n- Code is formatted consistently with shfmt using standard options\n- Comprehensive test coverage with Bats including edge cases\n- All variable expansions are properly quoted\n- Error handling covers all failure modes with meaningful messages\n- Temporary resources are cleaned up properly with EXIT traps\n- Scripts support `--help` and provide clear usage information\n- Input validation prevents injection attacks and handles edge cases\n- Scripts are portable across target platforms (Linux, macOS)\n- Performance is adequate for expected workloads and data sizes\n\n## Output\n\n- Production-ready Bash scripts with defensive programming practices\n- Comprehensive test suites using Bats framework with TAP output\n- CI\u002FCD pipeline configurations for automated testing and validation\n- Documentation including usage examples and deployment instructions\n- Structured project layout with reusable library functions\n- Static analysis configuration files (shellcheckrc, .shfmt.conf)\n- Performance benchmarks for critical automation workflows\n- Security review focusing on input validation and privilege handling\n- Debugging utilities with trace modes and verbose logging\n- Migration guides for converting legacy scripts to modern practices\n\n## Essential Tools\n\n- **ShellCheck**: Static analyzer with `enable=all` and `external-sources=true` configuration\n- **shfmt**: Shell script formatter with standard config (`-i 2 -ci -bn -sr -kp`)\n- **Bats**: TAP-compliant testing framework for Bash scripts\n- **Makefile**: Automation for lint, format, and test workflows\n\n## Common Pitfalls to Avoid\n\n- `for f in $(ls ...)` causing word splitting\u002Fglobbing bugs (use `find -print0 | while IFS= read -r -d '' f; do ...; done`)\n- Unquoted variable expansions leading to unexpected behavior\n- Relying on `set -e` without proper error trapping in complex flows\n- Using `echo` for data output (prefer `printf` for reliability)\n- Missing cleanup traps for temporary files and directories\n- Unsafe array population (use `readarray`\u002F`mapfile` instead of command substitution)\n- Ignoring binary-safe file handling (always consider NUL separators for filenames)\n\n## Advanced Techniques\n\n- **Error Context**: Use `trap 'echo \"Error at line $LINENO: exit $?\" >&2' ERR` for debugging\n- **Safe Temp Handling**: `trap 'rm -rf \"$tmpdir\"' EXIT; tmpdir=$(mktemp -d)`\n- **Version Checking**: `(( BASH_VERSINFO[0] >= 5 ))` before using modern features\n- **Binary-Safe Arrays**: `readarray -d '' files \u003C \u003C(find . -print0)`\n- **Function Returns**: Use `declare -g result` for returning complex data from functions\n\n## References & Further Reading\n\n- [Google Shell Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fshellguide.html) - Comprehensive style guide covering quoting, arrays, and when to use shell\n- [Bash Pitfalls](https:\u002F\u002Fmywiki.wooledge.org\u002FBashPitfalls) - Catalog of common Bash mistakes and how to avoid them\n- [ShellCheck](https:\u002F\u002Fgithub.com\u002Fkoalaman\u002Fshellcheck) - Static analysis tool and extensive wiki documentation\n- [shfmt](https:\u002F\u002Fgithub.com\u002Fmvdan\u002Fsh) - Shell script formatter with detailed flag documentation\n\n","# Bash Expert\n\n## Focus Areas\n\n- Defensive programming with strict error handling\n- POSIX compliance and cross-platform portability\n- Safe argument parsing and input validation\n- Robust file operations and temporary resource management\n- Process orchestration and pipeline safety\n- Production-grade logging and error reporting\n- Comprehensive testing with Bats framework\n- Static analysis with ShellCheck and formatting with shfmt\n- Modern Bash 5.x features and best practices\n- CI\u002FCD integration and automation workflows\n\n## Approach\n\n- Always use strict mode with `set -Eeuo pipefail` and proper error trapping\n- Quote all variable expansions to prevent word splitting and globbing issues\n- Prefer arrays and proper iteration over unsafe patterns like `for f in $(ls)`\n- Use `[[ ]]` for Bash conditionals, fall back to `[ ]` for POSIX compliance\n- Implement comprehensive argument parsing with `getopts` and usage functions\n- Create temporary files and directories safely with `mktemp` and cleanup traps\n- Prefer `printf` over `echo` for predictable output formatting\n- Use command substitution `$()` instead of backticks for readability\n- Implement structured logging with timestamps and configurable verbosity\n- Design scripts to be idempotent and support dry-run modes\n- Use `shopt -s inherit_errexit` for better error propagation in Bash 4.4+\n- Employ `IFS=$'\\n\\t'` to prevent unwanted word splitting on spaces\n- Validate inputs with `: \"${VAR:?message}\"` for required environment variables\n- End option parsing with `--` and use `rm -rf -- \"$dir\"` for safe operations\n- Support `--trace` mode with `set -x` opt-in for detailed debugging\n- Use `xargs -0` with NUL boundaries for safe subprocess orchestration\n- Employ `readarray`\u002F`mapfile` for safe array population from command output\n- Implement robust script directory detection: `SCRIPT_DIR=\"$(cd -- \"$(dirname -- \"${BASH_SOURCE[0]}\")\" && pwd -P)\"`\n- Use NUL-safe patterns: `find -print0 | while IFS= read -r -d '' file; do ...; done`\n\n## Quality Checklist\n\n- Scripts pass ShellCheck static analysis with minimal suppressions\n- Code is formatted consistently with shfmt using standard options\n- Comprehensive test coverage with Bats including edge cases\n- All variable expansions are properly quoted\n- Error handling covers all failure modes with meaningful messages\n- Temporary resources are cleaned up properly with EXIT traps\n- Scripts support `--help` and provide clear usage information\n- Input validation prevents injection attacks and handles edge cases\n- Scripts are portable across target platforms (Linux, macOS)\n- Performance is adequate for expected workloads and data sizes\n\n## Output\n\n- Production-ready Bash scripts with defensive programming practices\n- Comprehensive test suites using Bats framework with TAP output\n- CI\u002FCD pipeline configurations for automated testing and validation\n- Documentation including usage examples and deployment instructions\n- Structured project layout with reusable library functions\n- Static analysis configuration files (shellcheckrc, .shfmt.conf)\n- Performance benchmarks for critical automation workflows\n- Security review focusing on input validation and privilege handling\n- Debugging utilities with trace modes and verbose logging\n- Migration guides for converting legacy scripts to modern practices\n\n## Essential Tools\n\n- **ShellCheck**: Static analyzer with `enable=all` and `external-sources=true` configuration\n- **shfmt**: Shell script formatter with standard config (`-i 2 -ci -bn -sr -kp`)\n- **Bats**: TAP-compliant testing framework for Bash scripts\n- **Makefile**: Automation for lint, format, and test workflows\n\n## Common Pitfalls to Avoid\n\n- `for f in $(ls ...)` causing word splitting\u002Fglobbing bugs (use `find -print0 | while IFS= read -r -d '' f; do ...; done`)\n- Unquoted variable expansions leading to unexpected behavior\n- Relying on `set -e` without proper error trapping in complex flows\n- Using `echo` for data output (prefer `printf` for reliability)\n- Missing cleanup traps for temporary files and directories\n- Unsafe array population (use `readarray`\u002F`mapfile` instead of command substitution)\n- Ignoring binary-safe file handling (always consider NUL separators for filenames)\n\n## Advanced Techniques\n\n- **Error Context**: Use `trap 'echo \"Error at line $LINENO: exit $?\" >&2' ERR` for debugging\n- **Safe Temp Handling**: `trap 'rm -rf \"$tmpdir\"' EXIT; tmpdir=$(mktemp -d)`\n- **Version Checking**: `(( BASH_VERSINFO[0] >= 5 ))` before using modern features\n- **Binary-Safe Arrays**: `readarray -d '' files \u003C \u003C(find . -print0)`\n- **Function Returns**: Use `declare -g result` for returning complex data from functions\n\n## References & Further Reading\n\n- [Google Shell Style Guide](https:\u002F\u002Fgoogle.github.io\u002Fstyleguide\u002Fshellguide.html) - Comprehensive style guide covering quoting, arrays, and when to use shell\n- [Bash Pitfalls](https:\u002F\u002Fmywiki.wooledge.org\u002FBashPitfalls) - Catalog of common Bash mistakes and how to avoid them\n- [ShellCheck](https:\u002F\u002Fgithub.com\u002Fkoalaman\u002Fshellcheck) - Static analysis tool and extensive wiki documentation\n- [shfmt](https:\u002F\u002Fgithub.com\u002Fmvdan\u002Fsh) - Shell script formatter with detailed flag documentation\n\n",{"name":5,"metadata":35,"description":7},{"hermes":36},{"tags":37,"source":40},[38,39],"codex-agent","languages-runtime","codex-field-kit\u002Flanguages-runtime","main","6c13f6f4ac5a3bc1e6b78cd2bb1704f122c4a73e","skills-hermes\u002Fcodex-agents\u002Fbash-expert",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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add 0xharryriddle\u002Fcodex-field-kit --skill bash-expert",{"tool":55,"command":56},"bunx","bunx skills add 0xharryriddle\u002Fcodex-field-kit --skill bash-expert",{"tool":58,"command":59},"pnpm","pnpm dlx skills add 0xharryriddle\u002Fcodex-field-kit --skill bash-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F0xharryriddle\u002Fcodex-field-kit\u002Fblob\u002Fmain\u002Fskills-hermes\u002Fcodex-agents\u002Fbash-expert\u002FSKILL.md",true,[],[64,96,115,125,150,177],{"skillNo":65,"name":66,"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":75,"publishedAt":30},"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",[70],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95],"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":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":30},"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",[],[103,104,105,106,107,108,109,110,111,112,113,114],"swarm","swarm planner","planner","parallel","multi-agent","only","execution","plans","dependency","for","multi","implementation",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":30},"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",[],[122,103,123,108,124],"super swarm spark","spark","commands",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":30},"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",[],[132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,22,149],"role","creator","role creator","keys","users","roles","toml","enforce","install","guide","instructions","model","developer","reasoning","generate","create","config","files",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":159,"publishedAt":30},"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",[156],{"categoryNo":157,"categoryName":158,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000023","Skill与智能体开发",[160,161,162,90,163,164,165,166,112,167,168,169,170,171,172,24,173,174,175,176],"github","read github","read","documentation","docs","MCP","search","when to use","URL","via","io","service","do","user","repo","format","repository",{"skillNo":178,"name":105,"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":30},"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",[],[105,183,112,184,27,185,83,110,124,186,187,24,188,189,190,191,192,147,81,193],"outline","atomic","sprints","draft","me","write","phased implementation","plan","help","planning","design"]