[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7C9BV5ZW7JHTPVTKKG5Y25A":3,"skill-same:01M7C9BV5ZW7JHTPVTKKG5Y25A":55},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":6,"ownerDescription":39,"updatedAt":40,"install":41,"resources":54},"01M7C9BV5ZW7JHTPVTKKG5Y25A","dwarf-expert",null,"Provides expertise for analyzing DWARF debug files and understanding the DWARF debug format\u002Fstandard (v3-v5). Triggers when understanding DWARF information, interacting with DWARF files, answering DWARF-related questions, or working with code that parses DWARF data.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fdwarf-expert\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dwarf-expert\ndescription: Provides expertise for analyzing DWARF debug files and understanding the DWARF debug format\u002Fstandard (v3-v5). Triggers when understanding DWARF information, interacting with DWARF files, answering DWARF-related questions, or working with code that parses DWARF data.\nallowed-tools:\n  - Read\n  - Bash\n  - Grep\n  - Glob\n  - WebSearch\nrisk: unknown\nsource: community\n---\n# Overview\nThis skill provides technical knowledge and expertise about the DWARF standard and how to interact with DWARF files. Tasks include answering questions about the DWARF standard, providing examples of various DWARF features, parsing and\u002For creating DWARF files, and writing\u002Fmodifying\u002Fanalyzing code that interacts with DWARF data.\n\n## When to Use This Skill\n- Understanding or parsing DWARF debug information from compiled binaries\n- Answering questions about the DWARF standard (v3, v4, v5)\n- Writing or reviewing code that interacts with DWARF data\n- Using `dwarfdump` or `readelf` to extract debug information\n- Verifying DWARF data integrity with `llvm-dwarfdump --verify`\n- Working with DWARF parsing libraries (libdwarf, pyelftools, gimli, etc.)\n\n## When NOT to Use This Skill\n- **DWARF v1\u002Fv2 Analysis**: Expertise limited to versions 3, 4, and 5.\n- **General ELF Parsing**: Use standard ELF tools if DWARF data isn't needed.\n- **Executable Debugging**: Use dedicated debugging tools (gdb, lldb, etc) for debugging executable code\u002Fruntime behavior.\n- **Binary Reverse Engineering**: Use dedicated RE tools (Ghidra, IDA) unless specifically analyzing DWARF sections.\n- **Compiler Debugging**: DWARF generation issues are compiler-specific, not covered here.\n\n# Authoritative Sources\nWhen specific DWARF standard information is needed, use these authoritative sources:\n\n1. **Official DWARF Standards (dwarfstd.org)**: Use web search to find specific sections of the official DWARF specification at dwarfstd.org. Search queries like \"DWARF5 DW_TAG_subprogram attributes site:dwarfstd.org\" are effective.\n\n2. **LLVM DWARF Implementation**: The LLVM project's DWARF handling code at `llvm\u002Flib\u002FDebugInfo\u002FDWARF\u002F` serves as a reliable reference implementation. Key files include:\n   - `DWARFDie.cpp` - DIE handling and attribute access\n   - `DWARFUnit.cpp` - Compilation unit parsing\n   - `DWARFDebugLine.cpp` - Line number information\n   - `DWARFVerifier.cpp` - Validation logic\n\n3. **libdwarf**: The reference C implementation at github.com\u002Fdavea42\u002Flibdwarf-code provides detailed handling of DWARF data structures.\n\n# Verification Workflows\nUse `llvm-dwarfdump` verification options to validate DWARF data integrity:\n\n## Structural Validation\n```bash\n# Verify DWARF structure (compile units, DIE relationships, address ranges)\nllvm-dwarfdump --verify \u003Cbinary>\n\n# Detailed error output with summary\nllvm-dwarfdump --verify --error-display=full \u003Cbinary>\n\n# Machine-readable JSON error summary\nllvm-dwarfdump --verify --verify-json=errors.json \u003Cbinary>\n```\n\n## Quality Metrics\n```bash\n# Output debug info quality metrics as JSON\nllvm-dwarfdump --statistics \u003Cbinary>\n```\n\nThe `--statistics` output helps compare debug info quality across compiler versions and optimization levels.\n\n## Common Verification Patterns\n- **After compilation**: Verify binaries have valid DWARF before distribution\n- **Comparing builds**: Use `--statistics` to detect debug info quality regressions\n- **Debugging debuggers**: Identify malformed DWARF causing debugger issues\n- **DWARF tool development**: Validate parser output against known-good binaries\n\n# Parsing DWARF Debug Information\n## readelf\nELF files can be parsed via the `readelf` command ({baseDir}\u002Freference\u002Freadelf.md). Use this for general ELF information, but prefer `dwarfdump` for DWARF-specific parsing.\n\n## dwarfdump\nDWARF files can be parsed via the `dwarfdump` command, which is more effective at parsing and displaying complex DWARF information than `readelf` and should be used for most DWARF parsing tasks ({baseDir}\u002Freference\u002Fdwarfdump.md).\n\n# Working With Code\nThis skill supports writing, modifying, and reviewing code that interacts with DWARF data. This may involve code that parses DWARF debug data from scratch or code that leverages libraries to parse and interact with DWARF data ({baseDir}\u002Freference\u002Fcoding.md).\n\n# Choosing Your Approach\n```\n┌─ Need to verify DWARF data integrity?\n│   └─ Use `llvm-dwarfdump --verify` (see Verification Workflows above)\n├─ Need to answer questions about the DWARF standard?\n│   └─ Search dwarfstd.org or reference LLVM\u002Flibdwarf source\n├─ Need simple section dump or general ELF info?\n│   └─ Use `readelf` ({baseDir}\u002Freference\u002Freadelf.md)\n├─ Need to parse, search, and\u002For dump DWARF DIE nodes?\n│   └─ Use `dwarfdump` ({baseDir}\u002Freference\u002Fdwarfdump.md)\n└─ Need to write, modify, or review code that interacts with DWARF data?\n    └─ Refer to the coding reference ({baseDir}\u002Freference\u002Fcoding.md)\n```\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Overview\nThis skill provides technical knowledge and expertise about the DWARF standard and how to interact with DWARF files. Tasks include answering questions about the DWARF standard, providing examples of various DWARF features, parsing and\u002For creating DWARF files, and writing\u002Fmodifying\u002Fanalyzing code that interacts with DWARF data.\n\n## When to Use This Skill\n- Understanding or parsing DWARF debug information from compiled binaries\n- Answering questions about the DWARF standard (v3, v4, v5)\n- Writing or reviewing code that interacts with DWARF data\n- Using `dwarfdump` or `readelf` to extract debug information\n- Verifying DWARF data integrity with `llvm-dwarfdump --verify`\n- Working with DWARF parsing libraries (libdwarf, pyelftools, gimli, etc.)\n\n## When NOT to Use This Skill\n- **DWARF v1\u002Fv2 Analysis**: Expertise limited to versions 3, 4, and 5.\n- **General ELF Parsing**: Use standard ELF tools if DWARF data isn't needed.\n- **Executable Debugging**: Use dedicated debugging tools (gdb, lldb, etc) for debugging executable code\u002Fruntime behavior.\n- **Binary Reverse Engineering**: Use dedicated RE tools (Ghidra, IDA) unless specifically analyzing DWARF sections.\n- **Compiler Debugging**: DWARF generation issues are compiler-specific, not covered here.\n\n# Authoritative Sources\nWhen specific DWARF standard information is needed, use these authoritative sources:\n\n1. **Official DWARF Standards (dwarfstd.org)**: Use web search to find specific sections of the official DWARF specification at dwarfstd.org. Search queries like \"DWARF5 DW_TAG_subprogram attributes site:dwarfstd.org\" are effective.\n\n2. **LLVM DWARF Implementation**: The LLVM project's DWARF handling code at `llvm\u002Flib\u002FDebugInfo\u002FDWARF\u002F` serves as a reliable reference implementation. Key files include:\n   - `DWARFDie.cpp` - DIE handling and attribute access\n   - `DWARFUnit.cpp` - Compilation unit parsing\n   - `DWARFDebugLine.cpp` - Line number information\n   - `DWARFVerifier.cpp` - Validation logic\n\n3. **libdwarf**: The reference C implementation at github.com\u002Fdavea42\u002Flibdwarf-code provides detailed handling of DWARF data structures.\n\n# Verification Workflows\nUse `llvm-dwarfdump` verification options to validate DWARF data integrity:\n\n## Structural Validation\n```bash\n# Verify DWARF structure (compile units, DIE relationships, address ranges)\nllvm-dwarfdump --verify \u003Cbinary>\n\n# Detailed error output with summary\nllvm-dwarfdump --verify --error-display=full \u003Cbinary>\n\n# Machine-readable JSON error summary\nllvm-dwarfdump --verify --verify-json=errors.json \u003Cbinary>\n```\n\n## Quality Metrics\n```bash\n# Output debug info quality metrics as JSON\nllvm-dwarfdump --statistics \u003Cbinary>\n```\n\nThe `--statistics` output helps compare debug info quality across compiler versions and optimization levels.\n\n## Common Verification Patterns\n- **After compilation**: Verify binaries have valid DWARF before distribution\n- **Comparing builds**: Use `--statistics` to detect debug info quality regressions\n- **Debugging debuggers**: Identify malformed DWARF causing debugger issues\n- **DWARF tool development**: Validate parser output against known-good binaries\n\n# Parsing DWARF Debug Information\n## readelf\nELF files can be parsed via the `readelf` command ({baseDir}\u002Freference\u002Freadelf.md). Use this for general ELF information, but prefer `dwarfdump` for DWARF-specific parsing.\n\n## dwarfdump\nDWARF files can be parsed via the `dwarfdump` command, which is more effective at parsing and displaying complex DWARF information than `readelf` and should be used for most DWARF parsing tasks ({baseDir}\u002Freference\u002Fdwarfdump.md).\n\n# Working With Code\nThis skill supports writing, modifying, and reviewing code that interacts with DWARF data. This may involve code that parses DWARF debug data from scratch or code that leverages libraries to parse and interact with DWARF data ({baseDir}\u002Freference\u002Fcoding.md).\n\n# Choosing Your Approach\n```\n┌─ Need to verify DWARF data integrity?\n│   └─ Use `llvm-dwarfdump --verify` (see Verification Workflows above)\n├─ Need to answer questions about the DWARF standard?\n│   └─ Search dwarfstd.org or reference LLVM\u002Flibdwarf source\n├─ Need simple section dump or general ELF info?\n│   └─ Use `readelf` ({baseDir}\u002Freference\u002Freadelf.md)\n├─ Need to parse, search, and\u002For dump DWARF DIE nodes?\n│   └─ Use `dwarfdump` ({baseDir}\u002Freference\u002Fdwarfdump.md)\n└─ Need to write, modify, or review code that interacts with DWARF data?\n    └─ Refer to the coding reference ({baseDir}\u002Freference\u002Fcoding.md)\n```\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"description":7,"allowed-tools":26},"unknown","community",[27,28,29,30,31],"Read","Bash","Grep","Glob","WebSearch","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fdwarf-expert",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill dwarf-expert",{"tool":47,"command":48},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill dwarf-expert",{"tool":50,"command":51},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill dwarf-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-awesome-skills\u002Fskills\u002Fdwarf-expert\u002FSKILL.md",true,[],[56,63,70,77,84,91],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"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":83,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]