[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79YFNHHFNW7ECZGWMJAZ9RN":3,"skill-same:01M79YFNHHFNW7ECZGWMJAZ9RN":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":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},"01M79YFNHHFNW7ECZGWMJAZ9RN","arduino-developer",null,"Implement or fix Arduino sketches and libraries using the project-declared board, Arduino Core, version, and tooling. Use for Arduino IDE\u002FCLI or configured PlatformIO work when invoking arduino-developer.","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\u002Farduino-developer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: arduino-developer\ndescription: >-\n  Implement or fix Arduino sketches and libraries using the project-declared board, Arduino Core, version, and tooling. Use for Arduino IDE\u002FCLI or configured PlatformIO work when invoking arduino-developer.\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: arduino-developer\n\n## Trigger\n**Negative signal:** applies as defined in `_shared\u002Fskill-boilerplate.md`; the skill-specific signals are listed below.\n\nInvoke `arduino-developer` for Arduino sketches, libraries, board-specific firmware, or Arduino Core projects. Host examples: `\u002Farduino-developer`, `$arduino-developer`, `use skill arduino-developer`.\n\n## Outcome\n\nA configuration-aware implementation or diagnosis for the declared Arduino target. The skill identifies the board\u002Fmodule and revision, Arduino Core and version, dependency provenance, and the configured toolchain before recommending APIs or commands. It reports compile-only, upload, device runtime, and HIL evidence separately.\n\n## Lazy-load\n\n| When | Path |\n|------|------|\n| Scope and framework boundary | `references\u002Fscope.md` |\n| Orientation and execution flow | `references\u002Fexecute-flow.md` |\n| Forbidden assumptions and reporting limits | `references\u002Fmust-not.md` |\n| Embedded context and provenance | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fembedded-guidelines\u002FREADME.md`, `target-and-provenance.md`, `validation-and-reporting.md` |\n| Resources and communication | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fembedded-guidelines\u002Fresources-and-communication.md` |\n| Security and dependencies | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fembedded-guidelines\u002Fsecurity-and-dependencies.md` |\n| Repo context | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fstep-0-context.md` |\n| Before coding | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fstep-0.5-review-guidelines.md` |\n| Structure \u002F quality | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fcode-guidelines\u002Fprinciples\u002Fstructure-and-quality.md` |\n| Branching | `{{TOOLKIT_ROOT}}\u002Frules\u002Fbranch-validation.mdc`, `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fstep-3-branching.md` |\n| Pre-commit | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fstep-3.5-precommit-validation.md` |\n| Commit \u002F PR | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fstep-4-commits-pr.md` |\n| Pre-PR gate | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fstep-7-checklist.md` |\n| Subagent-first \u002F SPAWN.md | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fsubagent-first.md`, `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fagents\u002FSPAWN.md` |\n\nDo not preload unrelated stack packs or the whole memory bank. Load only the embedded topic needed for the current claim.\n\n**Never by default:** do not preload all `references\u002F*.md`, unrelated embedded or stack guideline packs, or target-specific hardware documentation. Load only the reference needed for the current claim after the board, core, version, tooling, and validation boundary are identified.\n\n## Process\n\n### Step -1b - Caveman Mode (Full cap)\n\n1. Read `{{SDD_ROOT}}\u002Fpreferences.json`.\n2. If `caveman_mode` is false, continue normally.\n3. If true, load `_shared\u002Fcaveman\u002FCAVEMAN.md`, apply the Full cap, and honor the session commands.\n\n### Subagent-first (before implement)\n\nClassify complexity, consult capability `subagents`, and load `SPAWN.md` plus `subagent-first.md`. Medium or complex work may use up to two children with scoped **paths** and a **receipt**; trivial work stays **in-parent**. If unavailable, use the documented **fallback** **in-parent** path.\n\n### 0. Establish the target context\n\nInspect the project before choosing an Arduino flow. Record each field as `confirmed`, `assumed`, `planned`, `implemented`, or `verified`:\n\n| Field | Required evidence |\n|------|-------------------|\n| Target | board\u002Fmodule, architecture, variant, and revision |\n| Runtime and core | Arduino runtime, Arduino Core family, exact version, and dependency source |\n| Tooling | Arduino IDE\u002FCLI or project-configured PlatformIO and its version |\n| Source and hardware provenance | project metadata, board specification, datasheet, measurement, or operator input |\n| Validation boundary | host-only, compile-only, device runtime, or HIL, with target and scenario |\n\nIf a material field is absent, ask for it or report the work as blocked. Do not select a board, core, API, pin, command, or capability from a family name alone.\n\n### Framework and toolchain decision\n\nTreat the framework and the toolchain as separate decisions. Before routing or recommending a command, require project evidence for all of the following:\n\n| Decision | Acceptable evidence | Result when absent |\n|---|---|---|\n| Arduino framework\u002Fcore | explicit Arduino Core or Arduino framework declaration, dependency metadata, Arduino CLI\u002FIDE project metadata, or operator-provided project evidence | do not route to this skill; ask for the framework and exact version |\n| Arduino Core version | pinned dependency\u002Fplatform version, lockfile, package metadata, or an explicit project record | block version-sensitive guidance; do not infer it from the board or library name |\n| Build\u002Fupload tool | Arduino IDE\u002FCLI configuration or command evidence; `platformio.ini`\u002Fequivalent with `framework = arduino` for PlatformIO | ask which configured tool is authoritative; do not introduce a tool |\n| Debug capability | configured debugger\u002Fprobe and target support, plus an observed debug session or project declaration | report debug as unavailable or unverified; do not equate compilation or serial logs with debug |\n\nFor ESP32 or ESP8266, a board name is never framework evidence. A native ESP-IDF project identified by `idf_component.yml`, `idf_component_register`, ESP-IDF CMake structure, `sdkconfig`, or `idf.py` scripts remains ESP-IDF-owned even when the board is ESP32\u002FESP8266. Route by the declared project framework, not by the board family. Keep MicroPython firmware and CPython host code outside this skill.\n\n### 1. Classify the Arduino artifact\n\nHandle `.ino` sketches, Arduino libraries, and board-specific firmware according to the project’s existing layout and dependency metadata. Preserve the declared library\u002Fcore versions and source provenance. Do not add a build system or dependency merely to fill a missing context.\n\nFor ESP32 or ESP8266, require evidence that the project uses the Arduino Core. Arduino Core may use platform internals, but it remains distinct from native ESP-IDF. Route native ESP-IDF projects to their own workflow; route MicroPython firmware to its own workflow; keep CPython host tools and tests with `python-developer`.\n\n### 2. Choose tooling from configuration\n\nUse Arduino IDE or Arduino CLI only when the project configuration, scripts, metadata, or operator evidence identifies it. Use PlatformIO only when its project configuration is present and relevant. Do not make PlatformIO the default and do not substitute `idf.py`, CMake, MicroPython tooling, or CPython commands for an Arduino flow without evidence.\n\nIf PlatformIO is selected, confirm that the relevant environment declares the Arduino framework; a `platformio.ini` containing only a board\u002Fplatform name is insufficient. If native ESP-IDF signals are present without an Arduino framework declaration, stop the Arduino flow and hand off to the ESP-IDF workflow. If neither framework nor toolchain is identifiable, request the smallest missing project evidence or report a bounded blocker.\n\n### 3. Implement and report narrowly\n\nApply the project’s selected core and board APIs, then label each result separately:\n\n- compile-only: source\u002Ftoolchain compatibility for the declared target;\n- upload: firmware transfer observed with the named board, port, and tool;\n- debug: an observed breakpoint\u002Ftrace\u002Fdebug-session result using the named debugger\u002Fprobe and target configuration;\n- device runtime: behavior observed on the named board\u002Frevision and configuration;\n- HIL: behavior observed with the named fixture, instruments, and scenario.\n\nA successful compile does not prove upload, debug, startup, peripherals, timing, electrical safety, runtime, or HIL. Serial output, logging, and a successful upload are not debug evidence. If the tool, board, core, version, or provenance is insufficient, request the missing data or stop with a bounded blocker.\n\n### 4. Review safety boundaries\n\nKeep Arduino Cloud guidance limited to firmware integration. Do not include dashboard or service administration. Never place credentials in source, examples, logs, or evidence. Qualify TLS, OTA, storage, memory, timing, pinout, voltage, and current claims by target, revision, library\u002Fcore version, and authoritative source.\n\n## Must not\n\n- Infer Arduino Core, ESP-IDF, MicroPython, or CPython from a board or family name alone.\n- Treat native ESP-IDF as an Arduino implementation or reuse `idf.py` without project evidence.\n- Treat a compile result as upload, device runtime, or HIL evidence.\n- Treat compile, upload, serial logging, or runtime observations as debug evidence without an observed debugger\u002Fprobe session.\n- Presume a universal Arduino IDE, CLI, PlatformIO, board revision, core version, pin map, TLS behavior, or OTA capability.\n- Put secrets, real credentials, or private keys in examples, logs, fixtures, or evidence.\n- Expand Arduino Cloud into dashboards or administration.\n- Paste guideline packs into child prompts, spawn for trivial work, or hard-fail when `subagents` is `none` or Agent is unavailable; use scoped paths, receipt, and fallback in-parent behavior.\n- Auto-commit, auto-push, or claim hardware validation that was not exercised.\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: arduino-developer\n\n## Trigger\n**Negative signal:** applies as defined in `_shared\u002Fskill-boilerplate.md`; the skill-specific signals are listed below.\n\nInvoke `arduino-developer` for Arduino sketches, libraries, board-specific firmware, or Arduino Core projects. Host examples: `\u002Farduino-developer`, `$arduino-developer`, `use skill arduino-developer`.\n\n## Outcome\n\nA configuration-aware implementation or diagnosis for the declared Arduino target. The skill identifies the board\u002Fmodule and revision, Arduino Core and version, dependency provenance, and the configured toolchain before recommending APIs or commands. It reports compile-only, upload, device runtime, and HIL evidence separately.\n\n## Lazy-load\n\n| When | Path |\n|------|------|\n| Scope and framework boundary | `references\u002Fscope.md` |\n| Orientation and execution flow | `references\u002Fexecute-flow.md` |\n| Forbidden assumptions and reporting limits | `references\u002Fmust-not.md` |\n| Embedded context and provenance | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fembedded-guidelines\u002FREADME.md`, `target-and-provenance.md`, `validation-and-reporting.md` |\n| Resources and communication | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fembedded-guidelines\u002Fresources-and-communication.md` |\n| Security and dependencies | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fembedded-guidelines\u002Fsecurity-and-dependencies.md` |\n| Repo context | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fstep-0-context.md` |\n| Before coding | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fstep-0.5-review-guidelines.md` |\n| Structure \u002F quality | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fcode-guidelines\u002Fprinciples\u002Fstructure-and-quality.md` |\n| Branching | `{{TOOLKIT_ROOT}}\u002Frules\u002Fbranch-validation.mdc`, `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fstep-3-branching.md` |\n| Pre-commit | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fstep-3.5-precommit-validation.md` |\n| Commit \u002F PR | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fstep-4-commits-pr.md` |\n| Pre-PR gate | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fstep-7-checklist.md` |\n| Subagent-first \u002F SPAWN.md | `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fdeveloper-common\u002Fsubagent-first.md`, `{{TOOLKIT_ROOT}}\u002Fskills\u002F_shared\u002Fagents\u002FSPAWN.md` |\n\nDo not preload unrelated stack packs or the whole memory bank. Load only the embedded topic needed for the current claim.\n\n**Never by default:** do not preload all `references\u002F*.md`, unrelated embedded or stack guideline packs, or target-specific hardware documentation. Load only the reference needed for the current claim after the board, core, version, tooling, and validation boundary are identified.\n\n## Process\n\n### Step -1b - Caveman Mode (Full cap)\n\n1. Read `{{SDD_ROOT}}\u002Fpreferences.json`.\n2. If `caveman_mode` is false, continue normally.\n3. If true, load `_shared\u002Fcaveman\u002FCAVEMAN.md`, apply the Full cap, and honor the session commands.\n\n### Subagent-first (before implement)\n\nClassify complexity, consult capability `subagents`, and load `SPAWN.md` plus `subagent-first.md`. Medium or complex work may use up to two children with scoped **paths** and a **receipt**; trivial work stays **in-parent**. If unavailable, use the documented **fallback** **in-parent** path.\n\n### 0. Establish the target context\n\nInspect the project before choosing an Arduino flow. Record each field as `confirmed`, `assumed`, `planned`, `implemented`, or `verified`:\n\n| Field | Required evidence |\n|------|-------------------|\n| Target | board\u002Fmodule, architecture, variant, and revision |\n| Runtime and core | Arduino runtime, Arduino Core family, exact version, and dependency source |\n| Tooling | Arduino IDE\u002FCLI or project-configured PlatformIO and its version |\n| Source and hardware provenance | project metadata, board specification, datasheet, measurement, or operator input |\n| Validation boundary | host-only, compile-only, device runtime, or HIL, with target and scenario |\n\nIf a material field is absent, ask for it or report the work as blocked. Do not select a board, core, API, pin, command, or capability from a family name alone.\n\n### Framework and toolchain decision\n\nTreat the framework and the toolchain as separate decisions. Before routing or recommending a command, require project evidence for all of the following:\n\n| Decision | Acceptable evidence | Result when absent |\n|---|---|---|\n| Arduino framework\u002Fcore | explicit Arduino Core or Arduino framework declaration, dependency metadata, Arduino CLI\u002FIDE project metadata, or operator-provided project evidence | do not route to this skill; ask for the framework and exact version |\n| Arduino Core version | pinned dependency\u002Fplatform version, lockfile, package metadata, or an explicit project record | block version-sensitive guidance; do not infer it from the board or library name |\n| Build\u002Fupload tool | Arduino IDE\u002FCLI configuration or command evidence; `platformio.ini`\u002Fequivalent with `framework = arduino` for PlatformIO | ask which configured tool is authoritative; do not introduce a tool |\n| Debug capability | configured debugger\u002Fprobe and target support, plus an observed debug session or project declaration | report debug as unavailable or unverified; do not equate compilation or serial logs with debug |\n\nFor ESP32 or ESP8266, a board name is never framework evidence. A native ESP-IDF project identified by `idf_component.yml`, `idf_component_register`, ESP-IDF CMake structure, `sdkconfig`, or `idf.py` scripts remains ESP-IDF-owned even when the board is ESP32\u002FESP8266. Route by the declared project framework, not by the board family. Keep MicroPython firmware and CPython host code outside this skill.\n\n### 1. Classify the Arduino artifact\n\nHandle `.ino` sketches, Arduino libraries, and board-specific firmware according to the project’s existing layout and dependency metadata. Preserve the declared library\u002Fcore versions and source provenance. Do not add a build system or dependency merely to fill a missing context.\n\nFor ESP32 or ESP8266, require evidence that the project uses the Arduino Core. Arduino Core may use platform internals, but it remains distinct from native ESP-IDF. Route native ESP-IDF projects to their own workflow; route MicroPython firmware to its own workflow; keep CPython host tools and tests with `python-developer`.\n\n### 2. Choose tooling from configuration\n\nUse Arduino IDE or Arduino CLI only when the project configuration, scripts, metadata, or operator evidence identifies it. Use PlatformIO only when its project configuration is present and relevant. Do not make PlatformIO the default and do not substitute `idf.py`, CMake, MicroPython tooling, or CPython commands for an Arduino flow without evidence.\n\nIf PlatformIO is selected, confirm that the relevant environment declares the Arduino framework; a `platformio.ini` containing only a board\u002Fplatform name is insufficient. If native ESP-IDF signals are present without an Arduino framework declaration, stop the Arduino flow and hand off to the ESP-IDF workflow. If neither framework nor toolchain is identifiable, request the smallest missing project evidence or report a bounded blocker.\n\n### 3. Implement and report narrowly\n\nApply the project’s selected core and board APIs, then label each result separately:\n\n- compile-only: source\u002Ftoolchain compatibility for the declared target;\n- upload: firmware transfer observed with the named board, port, and tool;\n- debug: an observed breakpoint\u002Ftrace\u002Fdebug-session result using the named debugger\u002Fprobe and target configuration;\n- device runtime: behavior observed on the named board\u002Frevision and configuration;\n- HIL: behavior observed with the named fixture, instruments, and scenario.\n\nA successful compile does not prove upload, debug, startup, peripherals, timing, electrical safety, runtime, or HIL. Serial output, logging, and a successful upload are not debug evidence. If the tool, board, core, version, or provenance is insufficient, request the missing data or stop with a bounded blocker.\n\n### 4. Review safety boundaries\n\nKeep Arduino Cloud guidance limited to firmware integration. Do not include dashboard or service administration. Never place credentials in source, examples, logs, or evidence. Qualify TLS, OTA, storage, memory, timing, pinout, voltage, and current claims by target, revision, library\u002Fcore version, and authoritative source.\n\n## Must not\n\n- Infer Arduino Core, ESP-IDF, MicroPython, or CPython from a board or family name alone.\n- Treat native ESP-IDF as an Arduino implementation or reuse `idf.py` without project evidence.\n- Treat a compile result as upload, device runtime, or HIL evidence.\n- Treat compile, upload, serial logging, or runtime observations as debug evidence without an observed debugger\u002Fprobe session.\n- Presume a universal Arduino IDE, CLI, PlatformIO, board revision, core version, pin map, TLS behavior, or OTA capability.\n- Put secrets, real credentials, or private keys in examples, logs, fixtures, or evidence.\n- Expand Arduino Cloud into dashboards or administration.\n- Paste guideline packs into child prompts, spawn for trivial work, or hard-fail when `subagents` is `none` or Agent is unavailable; use scoped paths, receipt, and fallback in-parent behavior.\n- Auto-commit, auto-push, or claim hardware validation that was not exercised.\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\u002Farduino-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 arduino-developer",{"tool":38,"command":39},"bunx","bunx skills add tibursocampos\u002Fagent-dev-toolkit --skill arduino-developer",{"tool":41,"command":42},"pnpm","pnpm dlx skills add tibursocampos\u002Fagent-dev-toolkit --skill arduino-developer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Farduino-developer\u002FSKILL.md",true,[46,52,56,60],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"reference.md","REFERENCE","参考文档",416,"https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Farduino-developer\u002Freference.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fexecute-flow.md",1793,"https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Farduino-developer\u002Freferences\u002Fexecute-flow.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fmust-not.md",1039,"https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Farduino-developer\u002Freferences\u002Fmust-not.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fscope.md",1122,"https:\u002F\u002Fgithub.com\u002Ftibursocampos\u002Fagent-dev-toolkit\u002Fblob\u002Fmaster\u002Fcore\u002Fskills\u002Farduino-developer\u002Freferences\u002Fscope.md",[65,72,79,86,93,100],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"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",[],[]]