[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79YH42CHF59YMCCYPRV2AAD":3,"skill-same:01M79YH42CHF59YMCCYPRV2AAD":68},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M79YH42CHF59YMCCYPRV2AAD","esp-idf-developer",null,"Implement or diagnose native ESP-IDF C\u002FC++ firmware using the project's declared target, ESP-IDF version, CMake configuration, idf.py workflow, and Component Manager metadata.","tibursocampos\u002Fagent-dev-toolkit","tibursocampos","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F37385246?v=4","01M79YF4CE4TH665XJJ7XSHXXK","Raphael Campos","01M79YF4D4KDQK01HZ6835E4A0",6,"MIT","https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Fesp-idf-developer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: esp-idf-developer\ndescription: >-\n  Implement or diagnose native ESP-IDF C\u002FC++ firmware using the project's declared\n  target, ESP-IDF version, CMake configuration, idf.py workflow, and Component Manager metadata.\n---\n\n## STOP - Read before ANY tool call\n\nRead `_shared\u002Fskill-boilerplate.md` first. It holds the guardrails read, the session gate rule, the user `sim` rule, the one-step rule, the gate check, and the user chat language rule. The steps below are skill-specific only.\n\n---\n\n# Skill: esp-idf-developer\n\n## Trigger\n**Negative signal:** applies as defined in `_shared\u002Fskill-boilerplate.md`; the skill-specific signals are listed below.\n\nInvoke for native ESP-IDF applications and components written in C or C++ when project evidence identifies ESP-IDF. A board name such as ESP32, ESP32-S3, or ESP32-C3 is not framework evidence by itself.\n\n## Outcome\n\nProvide configuration-aware implementation or diagnosis for the project's ESP-IDF target and version. Preserve the project's CMake and `idf.py` workflow, Component Manager resolution, and configuration files. Report unknown target or version context explicitly and keep compile-only evidence separate from device evidence.\n\n## Lazy-load\n\n| When | Path |\n|------|------|\n| Target, version, and framework evidence | `references\u002Fcontext-and-configuration.md` |\n| CMake, `idf.py`, and Component Manager workflow | `references\u002Fbuild-and-dependencies.md` |\n| Validation boundaries and safe reporting | `references\u002Fvalidation-and-safety.md` |\n| Forbidden assumptions and framework boundaries | `references\u002Fmust-not.md` |\n| Shared embedded WHAT layer | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fembedded-guidelines\u002FREADME.md`, `target-and-provenance.md`, `security-and-dependencies.md`, `validation-and-reporting.md` |\n\nDo not preload unrelated framework packs or the whole shared memory bank. Load only the reference needed for the current claim.\n\n**Never by default:** Do not preload unrelated framework packs, prescribe a universal ESP-IDF version or toolchain, or claim device\u002Fruntime evidence from a host-only or compile-only result.\n\n## Process\n\n### 0. Establish project evidence\n\nBefore recommending an API, command, target-specific option, or security feature, inspect the project and record the evidence state for:\n\n- target SoC, board\u002Fmodule, variant, and revision;\n- ESP-IDF version and provenance;\n- CMake project structure and authoritative build entry point;\n- `idf.py` availability and the observed installation\u002Fenvironment;\n- `idf_component.yml`, Component Manager lockfile, and dependency sources;\n- `sdkconfig.defaults`, generated local configuration, and any project-specific overrides;\n- validation boundary: host-only, compile-only, device runtime, or HIL.\n\nIf target or version evidence is missing, ask for it or state the uncertainty before using version-sensitive guidance. Never infer ESP-IDF from an ESP32 family name alone.\n\n### 1. Preserve the native workflow\n\nTreat the project's CMake files and `idf.py` commands as the build source of truth. Inspect existing components and registration before changing them. Use Component Manager metadata and its resolved lockfile as dependency evidence; do not silently replace resolved versions or introduce a new package manager.\n\nDistinguish versioned defaults such as `sdkconfig.defaults` from generated or local `sdkconfig` state. Compare configuration before changing it and preserve local state unless the operator explicitly requests a reviewed change.\n\n### 2. Condition host setup on observation\n\nGive PowerShell, ESP-IDF environment, and managed Python instructions only when the project or host inspection shows that installation and shell are applicable. Preserve the observed ESP-IDF installation and Python environment rather than prescribing a universal path, version, or activation command. A version mentioned by a preview project is project-specific evidence, never a global default for this skill or toolkit.\n\n### 3. Implement and report narrowly\n\nUse the project's C\u002FC++ layout and existing component boundaries. Label results separately as host-only, compile-only, device runtime, or HIL, and include the target, version, configuration, and observed command or scenario. A successful cross-build does not prove flashing, boot, peripheral behavior, timing, memory headroom, or HIL behavior.\n\nFor flash, erase, OTA, boot, secure-boot, encryption, signing, rollback, or provisioning guidance, require the target, version, bootloader\u002Fconfiguration, and recovery context first. Keep credentials, tokens, private keys, and device secrets out of source, configuration, logs, and evidence.\n\nBefore any flash, erase, or OTA operation, run the preflight in `references\u002Fvalidation-and-safety.md`: exact target, verified port or OTA channel, partition table, approved backup, and recovery evidence are all required. If one is missing, stop operation-specific guidance. Treat secure boot, flash encryption, signing, rollback, OTA, eFuse, and provisioning as separate decisions qualified by the actual SoC\u002Fversion\u002Fconfiguration and threat\u002Frecovery context.\n\n## Handoff\n\nFor a larger approved change, use `sdd-develop` with the canonical PLAN path. For a commit, use `commit`; for review, use `code-review`.\n","## STOP - Read before ANY tool call\n\nRead `_shared\u002Fskill-boilerplate.md` first. It holds the guardrails read, the session gate rule, the user `sim` rule, the one-step rule, the gate check, and the user chat language rule. The steps below are skill-specific only.\n\n---\n\n# Skill: esp-idf-developer\n\n## Trigger\n**Negative signal:** applies as defined in `_shared\u002Fskill-boilerplate.md`; the skill-specific signals are listed below.\n\nInvoke for native ESP-IDF applications and components written in C or C++ when project evidence identifies ESP-IDF. A board name such as ESP32, ESP32-S3, or ESP32-C3 is not framework evidence by itself.\n\n## Outcome\n\nProvide configuration-aware implementation or diagnosis for the project's ESP-IDF target and version. Preserve the project's CMake and `idf.py` workflow, Component Manager resolution, and configuration files. Report unknown target or version context explicitly and keep compile-only evidence separate from device evidence.\n\n## Lazy-load\n\n| When | Path |\n|------|------|\n| Target, version, and framework evidence | `references\u002Fcontext-and-configuration.md` |\n| CMake, `idf.py`, and Component Manager workflow | `references\u002Fbuild-and-dependencies.md` |\n| Validation boundaries and safe reporting | `references\u002Fvalidation-and-safety.md` |\n| Forbidden assumptions and framework boundaries | `references\u002Fmust-not.md` |\n| Shared embedded WHAT layer | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fembedded-guidelines\u002FREADME.md`, `target-and-provenance.md`, `security-and-dependencies.md`, `validation-and-reporting.md` |\n\nDo not preload unrelated framework packs or the whole shared memory bank. Load only the reference needed for the current claim.\n\n**Never by default:** Do not preload unrelated framework packs, prescribe a universal ESP-IDF version or toolchain, or claim device\u002Fruntime evidence from a host-only or compile-only result.\n\n## Process\n\n### 0. Establish project evidence\n\nBefore recommending an API, command, target-specific option, or security feature, inspect the project and record the evidence state for:\n\n- target SoC, board\u002Fmodule, variant, and revision;\n- ESP-IDF version and provenance;\n- CMake project structure and authoritative build entry point;\n- `idf.py` availability and the observed installation\u002Fenvironment;\n- `idf_component.yml`, Component Manager lockfile, and dependency sources;\n- `sdkconfig.defaults`, generated local configuration, and any project-specific overrides;\n- validation boundary: host-only, compile-only, device runtime, or HIL.\n\nIf target or version evidence is missing, ask for it or state the uncertainty before using version-sensitive guidance. Never infer ESP-IDF from an ESP32 family name alone.\n\n### 1. Preserve the native workflow\n\nTreat the project's CMake files and `idf.py` commands as the build source of truth. Inspect existing components and registration before changing them. Use Component Manager metadata and its resolved lockfile as dependency evidence; do not silently replace resolved versions or introduce a new package manager.\n\nDistinguish versioned defaults such as `sdkconfig.defaults` from generated or local `sdkconfig` state. Compare configuration before changing it and preserve local state unless the operator explicitly requests a reviewed change.\n\n### 2. Condition host setup on observation\n\nGive PowerShell, ESP-IDF environment, and managed Python instructions only when the project or host inspection shows that installation and shell are applicable. Preserve the observed ESP-IDF installation and Python environment rather than prescribing a universal path, version, or activation command. A version mentioned by a preview project is project-specific evidence, never a global default for this skill or toolkit.\n\n### 3. Implement and report narrowly\n\nUse the project's C\u002FC++ layout and existing component boundaries. Label results separately as host-only, compile-only, device runtime, or HIL, and include the target, version, configuration, and observed command or scenario. A successful cross-build does not prove flashing, boot, peripheral behavior, timing, memory headroom, or HIL behavior.\n\nFor flash, erase, OTA, boot, secure-boot, encryption, signing, rollback, or provisioning guidance, require the target, version, bootloader\u002Fconfiguration, and recovery context first. Keep credentials, tokens, private keys, and device secrets out of source, configuration, logs, and evidence.\n\nBefore any flash, erase, or OTA operation, run the preflight in `references\u002Fvalidation-and-safety.md`: exact target, verified port or OTA channel, partition table, approved backup, and recovery evidence are all required. If one is missing, stop operation-specific guidance. Treat secure boot, flash encryption, signing, rollback, OTA, eFuse, and provisioning as separate decisions qualified by the actual SoC\u002Fversion\u002Fconfiguration and threat\u002Frecovery context.\n\n## Handoff\n\nFor a larger approved change, use `sdd-develop` with the canonical PLAN path. For a commit, use `commit`; for review, use `code-review`.\n",{"name":5,"description":7},"master","d199760b9c98388be72a799dafccb9e981aa6d5f","core\u002Fskills\u002Fesp-idf-developer",0,"https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit","https:\u002F\u002Ftibursocampos.github.io\u002Fagent-dev-toolkit\u002F","https:\u002F\u002Fgithub.com\u002Ftibursocampos","2026-11-08 02:36:34",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add tibursocampos\u002Fagent-dev-toolkit --skill esp-idf-developer",{"tool":38,"command":39},"bunx","bunx skills add tibursocampos\u002Fagent-dev-toolkit --skill esp-idf-developer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tibursocampos\u002Fagent-dev-toolkit --skill esp-idf-developer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Fesp-idf-developer\u002FSKILL.md",true,[46,52,56,60,64],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"reference.md","REFERENCE","参考文档",569,"https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Fesp-idf-developer\u002Freference.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fbuild-and-dependencies.md",1530,"https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Fesp-idf-developer\u002Freferences\u002Fbuild-and-dependencies.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fcontext-and-configuration.md",2037,"https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Fesp-idf-developer\u002Freferences\u002Fcontext-and-configuration.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fmust-not.md",1076,"https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Fesp-idf-developer\u002Freferences\u002Fmust-not.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fvalidation-and-safety.md",3383,"https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Fesp-idf-developer\u002Freferences\u002Fvalidation-and-safety.md",[69,76,83,90,97,104],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79YNFMWYYP2QKV43VKJ90K0","user-own-skill","Operator-owned skill that is not part of the toolkit.","https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fscripts\u002Fvalidation\u002Ffixtures\u002Fseed-user-root\u002Fskills\u002Fuser-own-skill\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79YNCCEJ2J9MF2Q1WYXE265","vue-developer","Implement or fix small-to-medium Vue 3 features without full SDD (Composition API, Pinia, configured project test runner; Vitest is a fallback for new projects). Use for isolated Vue work or when invoking \u002Fvue-developer.","https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Fvue-developer\u002FSKILL.md",[],[],{"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":89,"publishedAt":19},"01M79YN85A2VGFD1P359F77YZ8","test-coverage","Run .NET Coverlet coverage, report Sonar-aligned metrics, and evaluate against a threshold (default 80%). Use for coverage reports or when invoking \u002Ftest-coverage.","https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Ftest-coverage\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M79YN42PG910XDKK6AKBJB1H","split-story-checklist","Break refined backlog steps into a dependency-aware task checklist (backend, frontend, tests). Prefer features\u002F... story folders. Use when breaking down tasks or invoking \u002Fsplit-story-checklist.","https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Fsplit-story-checklist\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M79YMZKTTY1NSH39AYN6YSYZ","sdd-spec","Create a PRD for a new feature or change (agent PRD .md; language per LANGUAGE.md + preferences under features\u002F). Feeds sdd-plan. Use when creating a spec or invoking \u002Fsdd-spec.","https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Fsdd-spec\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":19},"01M79YMV0YHHGCG527JEGY4RN0","sdd-plan","Create a baby-step PLAN from an existing PRD (agent PLAN .md; language per LANGUAGE.md + preferences). Feeds sdd-develop. Use when creating a plan or invoking \u002Fsdd-plan.","https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Fsdd-plan\u002FSKILL.md",[],[]]