New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Mspm0 Ccs

by mc3545dada in mc3545dada/mspm0-skill

Tool-neutral CLI agent rules for TI MSPM0 development with Code Composer Studio, Keil/uVision, CMake/GCC/OpenOCD, SysConfig, and DriverLib.

MITAuto-check passedAgent Workflows

Install Mspm0 Ccs

skills CLI
$ npx skills add mc3545dada/mspm0-skill --skill mspm0-ccs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mc3545dada/mspm0-skill mspm0-ccs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mc3545dada/mspm0-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mspm0-ccs .claude/skills/mspm0-ccs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
mspm0-ccs
GitHub stars
374
Token cost
~4.5k tokens
SKILL.md length
2,295 words
Files
58 (incl. scripts, references, assets)
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Tool-neutral CLI agent rules for TI MSPM0 development with Code Composer Studio, Keil/uVision, CMake/GCC/OpenOCD, SysConfig, and DriverLib.

  • Works in 8 steps: Locate the project .syscfg or… → Run python scripts/check_syscfg.py when… → Read .syscfg metadata: device, package,… → …
  • An agent needs to inspect
  • SKILL.md covers Default Workflow, Core Rules, Board-Specific Pin Caution and Project Shape Checks, plus 10 more sections
  • Calls python and cmake

What it does

Mspm0 Ccs is an agent skill from mc3545dada/mspm0-skill. Tool-neutral CLI agent rules for TI MSPM0 development with Code Composer Studio, Keil/uVision, CMake/GCC/OpenOCD, SysConfig, and DriverLib. Use when an agent needs to inspect or modify MSPM0 projects, edit .syscfg configuration, avoid generated SysConfig/build files, use DriverLib APIs, validate SysConfig output, package reusable MSPM0 examples, or work on NUEDC-style MSPM0 embedded firmware.

Its SKILL.md is about 4.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 63 other files, including scripts, reference files and assets (for example `assets/snippets/clock_80mhz_mfclk.syscfg.md`, `assets/snippets/gpio_output_led.syscfg.md` and `assets/snippets/mspm0g3507_lqfp64_empty_scaffold.syscfg.md`).

It sits in Agent Workflows, covering Agent instruction files. It works with C++ and Python. The repository describes itself as: 面向电赛的 MSPM0 + SysConfig Agent Skill. The licence is MIT.

When your agent uses it

  • An agent needs to inspect
  • Modify MSPM0 projects
  • Edit .syscfg configuration
  • Avoid generated SysConfig/build files

Example prompts

  • “/mspm0-ccs”

Requirements

  • Python 3

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Locate the project .syscfg or system.syscfg, editable source files, generated ti_msp_dl_config.h, and the active project entrypoint…
  2. Run python scripts/check_syscfg.py when this skill is available.
  3. Read .syscfg metadata: device, package, SDK product, SysConfig version, modules, instances, pins, clocks, and interrupts.
  4. Inspect generated ti_msp_dl_config.h for macro names, IRQ names, instance names, and the exact SysConfig init function spelling.
  5. Before adding unfamiliar SysConfig fields, inspect the user's existing .syscfg, examples/*/manifest.json, TI SDK examples, or…
  6. Modify the smallest relevant .syscfg and application-code surface.
  7. By default, make the smallest evidence-based .syscfg edit and run python scripts/run_sysconfig.py before rebuilding. Use CCS SysConfig MCP…
  8. If flashing or debugging, run python scripts/detect_probe.py or python scripts/check_syscfg.py --probe before selecting a backend. Confirm…

What it can do on your machine

Read from SKILL.md and the folder at commit 0cea5a0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    Shell commands in SKILL.md call:

    • python
    • cmake

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Mspm0 Ccs loads about 4.5k tokens when it runs, and up to ~15k if it reads all its reference files. Until then it costs about 101 tokens; SKILL.md has 2,295 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~101
When it runs · the whole SKILL.md, loaded when a task matches
~4.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~15k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mc3545dada/mspm0-skill at commit 0cea5a0, republished under its MIT licence (© mc3545dada). 2,295 words, ~4,505 tokens.

Download SKILL.mdSave it as .claude/skills/mspm0-ccs/SKILL.md (or your agent's skills folder). This skill also uses 57 other files; get the full folder from GitHub.
name
mspm0-ccs
description
Tool-neutral CLI agent rules for TI MSPM0 development with Code Composer Studio, Keil/uVision, CMake/GCC/OpenOCD, SysConfig, and DriverLib. Use when an agent needs to inspect or modify MSPM0 projects, edit .syscfg configuration, avoid generated SysConfig/build files, use DriverLib APIs, validate SysConfig output, package reusable MSPM0 examples, or work on NUEDC-style MSPM0 embedded firmware.

MSPM0 Agent Skill

Use this skill for TI MSPM0 firmware projects that use SysConfig and DriverLib through CCS / CCS Theia, Keil/uVision, or CMake + Arm GNU Toolchain + OpenOCD workflows. It is intended for Claude Code, OpenCode, OpenClaw, Continue, Cursor, Codex, and similar CLI/editor agents.

Default Workflow

  1. Locate the project .syscfg or system.syscfg, editable source files, generated ti_msp_dl_config.h, and the active project entrypoint: targetConfigs/*.ccxml for CCS, *.uvprojx plus scatter file for Keil/uVision, or CMakeLists.txt plus OpenOCD .cfg files for CMake/GCC/OpenOCD.
  2. Run python scripts/check_syscfg.py <project-dir> when this skill is available.
  3. Read .syscfg metadata: device, package, SDK product, SysConfig version, modules, instances, pins, clocks, and interrupts.
  4. Inspect generated ti_msp_dl_config.h for macro names, IRQ names, instance names, and the exact SysConfig init function spelling.
  5. Before adding unfamiliar SysConfig fields, inspect the user's existing .syscfg, examples/*/manifest.json, TI SDK examples, or source/ti/driverlib/.meta/*.syscfg.js.
  6. Modify the smallest relevant .syscfg and application-code surface.
  7. By default, make the smallest evidence-based .syscfg edit and run python scripts/run_sysconfig.py <project-dir> before rebuilding. Use CCS SysConfig MCP only when the user explicitly requests it or the current session already exposes a confirmed SysConfig MCP tool.
  8. If flashing or debugging, run python scripts/detect_probe.py or python scripts/check_syscfg.py <project-dir> --probe before selecting a backend. Confirm the configured probe matches the connected hardware and prefer a System Reset after programming.

Core Rules

  • Treat .syscfg as the source of truth for pinmux, peripheral setup, clocks, interrupts, DMA ownership, and generated initialization.
  • Prefer SysConfig + DriverLib for GPIO, UART, PWM, Timer, ADC, I2C, SPI, DMA, and clock setup.
  • Do not hand-edit generated outputs such as Debug/ti_msp_dl_config.c, Debug/ti_msp_dl_config.h, the project-root ti_msp_dl_config.c / ti_msp_dl_config.h pair in Keil layouts, device_linker.cmd, Objects/, Listings/, object files, maps, or .out files.
  • Preserve .syscfg metadata such as @cliArgs, @v2CliArgs, @versions, --device, --package, and --product.
  • Do not guess generated names. Read ti_msp_dl_config.h and use the local macros and the local init function spelling, such as SYSCFG_DL_init().
  • Do not invent SysConfig fields, enum values, device metadata, board names, package names, or tool versions. Validate against local examples, SDK metadata, or SysConfig CLI.
  • New SysConfig releases may explicitly recommend the CCS SysConfig MCP. This skill does not probe for or require that unverified backend by default: use it only when the user asks for MCP or the current session already exposes a confirmed SysConfig MCP tool. Otherwise use a minimal manual edit followed immediately by standalone CLI validation, and state that this does not provide the MCP's interactive mutation feedback.
  • Preserve unrelated user code, comments, copyright headers, project layout, and existing .syscfg settings. If a requested feature requires a larger rewrite, explain why before making it when possible.
  • Do not change device, package, SDK, compiler, CCS version, board, or debug probe without user confirmation.
  • If the user asks only to "flash" or "debug", do not silently assume J-Link, XDS110, CMSIS-DAP/DAPLink, or ST-Link. Detect the connected probe first. If detection is unknown, multiple probes are connected, or the project configuration conflicts with the physical probe, stop and ask the user which backend to use.
  • Treat an empty probe-detector result as inconclusive, not proof that no probe is connected. Some DAPLink/CMSIS-DAP and XDS110 devices appear only as Windows USBDevice, HIDClass, or Ports children. Inspect OS USB/PnP devices and serial ports (python scripts/serial_console.py --list on Windows), then try the intended backend's read-only probe/list command or ask the user before concluding the probe is absent.
  • If SysConfig emits warnings, report them separately from build/flash success. Do not call a warning-producing generation "clean".
  • If hardware behavior is not verified on a connected board, say that validation stopped at source, SysConfig, or build level.

Board-Specific Pin Caution

When the user explicitly says the board is LCKFB Tianmengxing MSPM0G3507:

  • Avoid choosing A21/PA21, A23/PA23, A02/PA02, and A18/PA18 for ordinary user-requested pin assignments unless the user asks for those pins or the local project already deliberately uses them.
  • PA10 and PA11 are also marked as special, but Tianmengxing routes them as the default UART pins. When choosing pins for a UART, consider PA10 TX and PA11 RX first if they are free and match the requested UART instance. For GPIO, PWM, SPI, I2C, timer, or other non-UART uses, continue to treat PA10/PA11 as special pins and prefer other available pins.
  • If the user asks to drive or reuse one of these special pins for a non-default purpose, remind them of the Tianmengxing board note. In particular, explain that repurposing PA10/PA11 can conflict with or remove the board's default UART connection.
  • Do not silently move an existing project away from these pins. Explain the board caveat first, then ask or proceed according to the user's intent.

Project Shape Checks

  • Simple projects usually keep most logic in main.c, empty.c, or a small number of files. It is acceptable to make narrowly scoped edits there.
  • Framework projects often have multiple source directories such as app/, bsp/, components/, core/, drivers/, hal/, middleware/, or tasks/. First identify ownership boundaries before adding peripherals or changing control logic.
  • Do not assume every MSPM0 project is CCS-like or single-file. A framework project can still use CCS, Keil, or CMake/GCC/OpenOCD.
  • For control code, confirm whether timing comes from a timer ISR, RTOS task delay, hardware PWM/ADC trigger chain, or a main-loop poll before changing periods or priorities.

Keil Project Checks

  • Treat system.syscfg and ti_msp_dl_config.c / ti_msp_dl_config.h as the configuration source surface for Keil-based MSPM0 projects that keep SysConfig outputs at the project root.
  • Treat a Keil .uvprojx as the project entrypoint, the scatter file as the linker source of truth, and Objects/, Listings/, *.uvoptx, build logs, and generated outputs as inspection-only unless a request explicitly targets them.
  • For a project's application code, follow its own source layout rather than assuming CCS defaults.

CMake / GCC / OpenOCD Checks

  • Treat CMakeLists.txt, toolchain files, and OpenOCD .cfg files as the project entrypoints for CMake/GCC/OpenOCD projects.
  • Build through the existing CMake build directory when present, for example cmake --build cmake-build-debug --target <target>.
  • MSPM0 OpenOCD flashing usually requires a TI MSPM0-capable OpenOCD build or TI extension branch. If OpenOCD reports unable to find a matching CMSIS-DAP device, report that as probe discovery failure rather than firmware failure.
  • Do not require CCS targetConfigs/*.ccxml when the active project uses OpenOCD instead of DSLite.

FreeRTOS Checks

  • If FreeRTOSConfig.h, FreeRTOS.h, task.h, xTaskCreate, or vTaskStartScheduler are present, treat the project as RTOS-aware.
  • Keep RTOS handling lightweight: respect existing task, queue, ISR, and blocking-call boundaries; do not impose a specific framework architecture unless the user asks.

Ambiguous Requests

If the user omits important hardware parameters, do not silently choose risky values.

  • For low-risk defaults, use this skill's examples/ or local TI SDK examples, then tell the user which defaults were applied.
  • For important parameters, ask before editing and offer a concrete recommendation.
  • Important missing parameters include pin, peripheral instance, UART baud/data/parity/stop bits, Timer period, PWM frequency/duty/polarity, ADC channel/reference/sample time, DMA direction/source/destination, interrupt priority, and external-module power/logic levels.

Example: if the user asks "add a timer interrupt", ask which timer and period they want, and recommend a starter such as TIMG at 1 ms or 10 ms if they are unsure.

External Modules And Hardware Debugging

When asked to drive an external module, sensor, motor driver, servo, display, radio, or custom board:

  • Ask for the module datasheet, schematic, pin map, supply voltage, logic level, communication protocol, and key parameters when they are not available.
  • Verify wiring assumptions before blaming code: power, ground, pull-ups, level shifting, reset/enable pins, boot pins, chip select, UART TX/RX crossover, I2C address, SPI mode, PWM polarity, and shared pins.
  • If repeated attempts fail and SysConfig, build, flash, and code logic look correct, explicitly raise the possibility of wiring, power, module mode, datasheet mismatch, damaged hardware, or wrong test procedure.
  • Separate "firmware looks correct" from "hardware proved correct".

Reference Selection

Read references only when needed:

  • references/project_workflows.md: .syscfg editing, CCS / Keil / CMake project layout, SDK schema lookup, SysConfig CLI, builds, DSLite/J-Link, and OpenOCD.
  • references/driverlib_runtime_rules.md: DriverLib usage, interrupts, clock tree, delays, and common runtime mistakes.
  • references/hardware_validation_notes.md: verified Tianmengxing MSPM0G3507 lessons, HFXT warnings, flash/reset behavior, and real-board caveats.
  • references/debug_backends.md: CCS-DSS and OpenOCD/GDB probe, flash, breakpoint, retry, and manual-unlock workflows.

Use examples/ as one source for reusable tested patterns. Prefer scripts/list_examples.py to inspect available examples before opening individual example files, but do not assume packaged examples outrank the user's existing project structure or official TI SDK examples.

Show full SKILL.md (926 more words)Show less

Examples

Each reusable example should contain:

text
examples/<name>/
├─ example.syscfg
├─ README.md
├─ manifest.json
└─ src/
   └─ source files copied from the minimal relevant project surface

Do not require users to drop full CCS projects into examples/. Use scripts/capture_example.py to extract a compact example package from a real project.

When applying an example to a user project:

  • Treat skill examples as proven references, not mandatory project templates.
  • Copy only the needed .syscfg fields, generated-name expectations, code pattern, or debugging lesson.
  • Preserve the user's existing file layout and naming. If an example uses BSP/, do not create BSP/ in the user project unless the user asked for that structure or the project already follows it.
  • Prefer the user's local style when it conflicts with an example's directory names, wrapper names, or layering.
  • Consider official TI SDK examples and local SDK metadata at the same or higher priority when they better match the user's board, SDK version, peripheral, or toolchain.
  • For DMA UART examples, keep TX buffers per UART instance, avoid shared static printf buffers, and choose RX handling per port: ISR callback for the one port that needs immediate line parsing, UART_poll() for extra receive ports, or TX-only init for ports that do not receive.
  • For periodic timer interrupts, configure the TIMER instance and interrupt in .syscfg, confirm the generated load value against the generated CPU clock, enable the generated IRQ in application code, and keep the ISR short.

Tools

Run bundled scripts with Python 3.10 or newer. serial_console.py additionally requires pyserial; if import fails, tell the user to run python -m pip install pyserial. TI SDK, SysConfig, CCS/UniFlash, OpenOCD, and GDB remain external workflow dependencies and are not installed by this skill.

  • python scripts/check_syscfg.py <project-dir>: static project check for .syscfg, generated files, pins, init spelling, project shape, CCS/Keil/CMake/OpenOCD clues, build output, target config, and validation hints.
  • python scripts/run_sysconfig.py <project-dir>: discover the project-declared SysConfig and MSPM0 SDK versions, then validate the selected .syscfg into an isolated temporary directory without overwriting project outputs. Use --tool or --product only for an intentional explicit override.
  • python scripts/detect_probe.py: read-only connected-probe detection for common CMSIS-DAP/DAPLink, J-Link, XDS110, and ST-Link hardware; an empty result is explicitly inconclusive and requires OS/backend fallback checks.
  • python scripts/check_syscfg.py <project-dir> --probe: run the static check, detect connected probes, compare them with project hints, and suppress unsafe flash suggestions when a CCS .ccxml conflicts with the physical probe.
  • python scripts/list_examples.py: list packaged examples from examples/*/manifest.json.
  • python scripts/capture_example.py <project-dir> --name <example-name> --include <glob>: package selected source files and .syscfg from a user project into examples/<example-name>/.
  • python scripts/index_syscfg_examples.py <mspm0-sdk-root> --board LP_MSPM0G3507 --module UART: search local TI SDK examples and module metadata.
  • python scripts/serial_console.py --list: list serial ports.
  • python scripts/ccs_dss_debug.py <project-dir> probe --leave-running: connect through CCS Debug Server Scripting, read reset/register state, verify the configured .ccxml debug path, and continue the target before disconnecting.
  • python scripts/ccs_dss_debug.py <project-dir> load-symbols --symbol main: load debug symbols from .out without programming flash.
  • python scripts/openocd_debug.py <project-dir> probe: connect through OpenOCD, halt briefly, report target state, and resume.
  • python scripts/openocd_debug.py <project-dir> flash: flash, verify, and reset-run an auto-detected .out, .elf, .axf, or .hex output through OpenOCD.
  • python scripts/openocd_debug.py <project-dir> run-to-symbol --symbol main: use OpenOCD + arm-none-eabi-gdb to reset and run to a symbol breakpoint.

For the verified CH340 setup, use python scripts/serial_console.py -p COM6 -b 115200 --timestamp --duration 10 after closing other serial tools such as VOFA+. For line-based MCU parsers, send one test frame and wait for the echo with python scripts/serial_console.py -p COM6 -b 115200 --send "ping" --send-line --timestamp --duration 3. Use --send-hex "00 00 80 3F" when testing binary payloads.

Flash Backends

Before selecting a flash backend for a vague request such as "flash this project", run:

text
python scripts/detect_probe.py
python scripts/check_syscfg.py <project-dir> --probe

Probe detection is read-only. Do not flash when multiple probes are connected, detection is unknown, or the physical probe conflicts with the project configuration until the user confirms the intended backend. On Windows, if no probe is identified, inspect Get-PnpDevice -PresentOnly and python scripts/serial_console.py --list; a debug probe may expose a CMSIS-DAP/XDS interface or virtual COM port outside the generic USB device class.

The verified CCS flash path is DSLite / UniFlash with J-Link. For automated flashing after clock-tree changes, prefer DSLite System Reset:

text
dslite -c <target.ccxml> -e -r 2 -u <project.out>

For CMake/GCC/OpenOCD projects, use the project's existing flash target or explicit OpenOCD config. The packaged openocd_debug.py helper can also flash an existing compatible output. Keep the backend explicit and report probe-discovery errors separately from build success.

Debug Backends

Keep CCS-DSS and OpenOCD/GDB as separate backends. Read references/debug_backends.md before debugging or diagnosing repeated probe failures.

For CCS / CCS Theia / UniFlash-style projects with a matching targetConfigs/*.ccxml:

text
python scripts/ccs_dss_debug.py <project-dir> probe --leave-running

For OpenOCD-capable MSPM0 projects:

text
python scripts/openocd_debug.py <project-dir> probe

The CCS-DSS physical probe is selected by .ccxml; it is not inherently J-Link-only. Use symbol-only loading when firmware is already flashed and rewriting flash is unnecessary. For OpenOCD, do not run concurrent operations against one probe. Neither backend should silently issue destructive recovery. If a target appears locked or protected, first separate probe/wiring/reset faults, application startup faults, SWD password or security policy, invalid NONMAIN configuration, and an interrupted-flash recovery state. On a Tianmengxing MSPM0G3507, a readable SWD DPIDR followed by repeated Could not find MEM-AP to control the core errors was reproduced after programming was interrupted; follow the UART BSL recovery boundary in references/debug_backends.md instead of treating this as proof that the probe is absent. With CCS-DSS and a matching XDS target configuration, a read-only CFGAP_BOOTDIAG check can work even when the Cortex-M0+ session cannot connect. Only use BSL Mass Erase, DSSM Mass Erase, or Factory Reset after the user explicitly authorizes data loss, and follow references/debug_backends.md; never infer success from a reset pulse or a timed-out command. Debug actions can halt the CPU, so report that risk before using breakpoints or register inspection on real-time control hardware.

© mc3545dada, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 57 other files (scripts, references, assets) in skills/mspm0-ccs of mc3545dada/mspm0-skill.

  • SKILL.md
  • assets/snippets/clock_80mhz_mfclk.syscfg.md
  • assets/snippets/gpio_output_led.syscfg.md
  • assets/snippets/mspm0g3507_lqfp64_empty_scaffold.syscfg.md
  • assets/snippets/timer_irq_1ms_pb22.syscfg.md
  • assets/snippets/uart0_blocking_tx.syscfg.md
  • assets/snippets/uart0_dma_tx_irq_rx.syscfg.md
  • examples/empty_project/README.md
  • examples/empty_project/empty.syscfg
  • examples/empty_project/manifest.json
  • examples/empty_project/src/empty.c
  • examples/led_blink/README.md
  • examples/led_blink/example.syscfg
  • examples/led_blink/manifest.json
  • examples/led_blink/src
  • … and 43 more

Open the folder on GitHubat commit 0cea5a0

Compare with similar skills

Mspm0 Ccs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Mspm0 Ccs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mspm0 Ccs this skillmc3545dada/mspm0-skill374—~4.5kAutomated safety check: PassMIT
Generate AI Rulesdivar-ir/ai-doc-gen767—~1.2kAutomated safety check: PassMIT
Goal Prompt Builderwin4r/goal-prompt-builder229—~3.1kAutomated safety check: PassMIT
Requirement Ledger CLI Workflowadand-91/gpt-6-astra-skill126—~1.5kAutomated safety check: PassMIT
Analyze Codebasedivar-ir/ai-doc-gen767—~899Automated safety check: PassMIT
Lintlanghermes-labs-ai/lintlang138—~1.7kAutomated safety check: PassApache-2.0

Similar skills

  • Generate AI Rules

    divar-ir/ai-doc-gen

    Generate AI assistant configuration files for a repository — CLAUDE.md, AGENTS.md, and Cursor rules (.cursor/rules/.mdc) — from codebase analysis.

    767 GitHub stars~1.2k tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed

  • Goal Prompt Builder

    win4r/goal-prompt-builder

    Build high-quality /goal commands for OpenAI Codex CLI 0.128+ that maximize audit-friendliness and minimize false-completion.

    229 GitHub stars~3.1k tokensUpdated 5 mo ago
    Agent WorkflowsAuto-check passed

  • Requirement Ledger CLI Workflow

    adand-91/gpt-6-astra-skill

    Runs an evidence-bound audit, daily or weekly review through the requirement-ledger CLI, binding scope and authority first and blocking the final report until a handoff check passes.

    126 GitHub stars~1.5k tokensUpdated 23 days ago
    Agent WorkflowsAuto-check passed

  • Analyze Codebase

    divar-ir/ai-doc-gen

    Run a multi-agent deep analysis of a codebase, producing AI-readable analysis documents in .ai/docs/ covering structure, dependencies, data flow, request flow, and APIs.

    767 GitHub stars~899 tokensUpdated 2 mo ago
    Agent WorkflowsAuto-check passed

  • Lintlang

    hermes-labs-ai/lintlang

    Lint AI agent instruction files (SKILL.md, CLAUDE.md, AGENTS.md, GEMINI.md), tool definitions, system prompts, and agent configs with the deterministic LintLang CLI.

    138 GitHub stars~1.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Setup Engine

    pixel-cellar/Claude-Code-Game-Studios

    配置项目的游戏引擎和版本。将引擎锁定到 CLAUDE.md 中，检测知识缺口，当版本超出 LLM 训练数据时通过 WebSearch 填充引擎参考文档。

    346 GitHub stars~1.5k tokensUpdated 6 mo ago
    Agent WorkflowsAuto-check passed

Works with

Categories

Questions about Mspm0 Ccs

What does Mspm0 Ccs do?

Tool-neutral CLI agent rules for TI MSPM0 development with Code Composer Studio, Keil/uVision, CMake/GCC/OpenOCD, SysConfig, and DriverLib. Mspm0 Ccs is an agent skill from mc3545dada/mspm0-skill. Tool-neutral CLI agent rules for TI MSPM0 development with Code Composer Studio, Keil/uVision, CMake/GCC/OpenOCD, SysConfig, and DriverLib.

When should I use Mspm0 Ccs?

Mspm0 Ccs fits situations like: an agent needs to inspect; modify MSPM0 projects; edit .syscfg configuration; avoid generated SysConfig/build files.

How do I install Mspm0 Ccs in Claude Code?

Run `npx skills add mc3545dada/mspm0-skill --skill mspm0-ccs -a claude-code`. Or copy the skill folder (skills/mspm0-ccs in mc3545dada/mspm0-skill) into .claude/skills/mspm0-ccs in your project. Claude Code loads it when a task matches its description.

How do I install Mspm0 Ccs in Codex?

Run `npx skills add mc3545dada/mspm0-skill --skill mspm0-ccs -a codex`. Or copy the skill folder (skills/mspm0-ccs in mc3545dada/mspm0-skill) into .agents/skills/mspm0-ccs in your project. Codex loads it when a task matches its description.

Can I use Mspm0 Ccs in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mc3545dada/mspm0-skill --skill mspm0-ccs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mspm0-ccs, .gemini/skills/mspm0-ccs, .github/skills/mspm0-ccs and .opencode/skills/mspm0-ccs in your project.

What does Mspm0 Ccs need to run?

Going by SKILL.md and its folder, Mspm0 Ccs needs the command-line tools its instructions call (python and cmake). Our summary lists: Python 3.

Does Mspm0 Ccs access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Mspm0 Ccs safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Mspm0 Ccs use?

Mspm0 Ccs is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Mspm0 Ccs use?

About 4.5k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 10k tokens, read only when the agent opens those files.

What are the alternatives to Mspm0 Ccs?

Skills that share tags, products or a category with Mspm0 Ccs: Generate AI Rules (divar-ir/ai-doc-gen, 767 stars), Goal Prompt Builder (win4r/goal-prompt-builder, 229 stars), Requirement Ledger CLI Workflow (adand-91/gpt-6-astra-skill, 126 stars) and Analyze Codebase (divar-ir/ai-doc-gen, 767 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mspm0 Ccs?

mc3545dada (a GitHub user) maintains it in mc3545dada/mspm0-skill, which has 374 GitHub stars. The repository was last updated on July 28, 2026.

Source: mc3545dada/mspm0-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.