Official agent skill

Systemc Tools

A skill your agent uses when writing, editing, reviewing, or debugging synthesizable SystemC code for Intel SystemC Compiler (ICSC) and SingleSource library.

OfficialCustom licenceAuto-check passedDevelopment

Install Systemc Tools

skills CLI

$ npx skills add intel/systemc-compiler --skill systemc-tools -a claude-code

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

GitHub CLI

$ gh skill install intel/systemc-compiler systemc-tools --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/intel/systemc-compiler.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/systemc-tools .claude/skills/systemc-tools && 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/

Paste into Claude Code

Install the "systemc-tools" agent skill from https://github.com/intel/systemc-compiler/tree/main/.github/skills/systemc-tools into .claude/skills/systemc-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systemc-tools", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/intel/systemc-compiler/tree/main/.github/skills/systemc-tools

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add intel/systemc-compiler --skill systemc-tools -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install intel/systemc-compiler systemc-tools --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/intel/systemc-compiler.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/systemc-tools .agents/skills/systemc-tools && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "systemc-tools" agent skill from https://github.com/intel/systemc-compiler/tree/main/.github/skills/systemc-tools into .agents/skills/systemc-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systemc-tools", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add intel/systemc-compiler --skill systemc-tools -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install intel/systemc-compiler systemc-tools --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/intel/systemc-compiler.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/systemc-tools .cursor/skills/systemc-tools && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "systemc-tools" agent skill from https://github.com/intel/systemc-compiler/tree/main/.github/skills/systemc-tools into .cursor/skills/systemc-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systemc-tools", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/intel/systemc-compiler.git --path .github/skills/systemc-tools

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add intel/systemc-compiler --skill systemc-tools -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install intel/systemc-compiler systemc-tools --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/intel/systemc-compiler.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/systemc-tools .gemini/skills/systemc-tools && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "systemc-tools" agent skill from https://github.com/intel/systemc-compiler/tree/main/.github/skills/systemc-tools into .gemini/skills/systemc-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systemc-tools", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install intel/systemc-compiler systemc-tools

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add intel/systemc-compiler --skill systemc-tools -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/intel/systemc-compiler.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/systemc-tools .github/skills/systemc-tools && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "systemc-tools" agent skill from https://github.com/intel/systemc-compiler/tree/main/.github/skills/systemc-tools into .github/skills/systemc-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systemc-tools", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add intel/systemc-compiler --skill systemc-tools -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install intel/systemc-compiler systemc-tools --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/intel/systemc-compiler.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/systemc-tools .opencode/skills/systemc-tools && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "systemc-tools" agent skill from https://github.com/intel/systemc-compiler/tree/main/.github/skills/systemc-tools into .opencode/skills/systemc-tools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "systemc-tools", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: systemc-tools
GitHub stars: 320
Token cost: ~4.4k tokens
SKILL.md length: 2,212 words
Files: 1
Skills in repo: 1
Repo updated: Sep 25, 2026
First seen: Oct 7, 2026
Licence: Custom licence

At a glance

A skill your agent uses when writing, editing, reviewing, or debugging synthesizable SystemC code for Intel SystemC Compiler (ICSC) and SingleSource library.

Works in 7 steps: Identify the task type: implementation,… → Read the nearby code first: module… → Check synthesis constraints before… → …
Debugging synthesizable SystemC code for Intel SystemC Compiler (ICSC) and SingleSource library
SKILL.md covers Workflow, Project Structure, Module Hierarchy and Modules And Modular Interfaces, plus 18 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Systemc Tools is an agent skill from intel/systemc-compiler, published by the product's own GitHub organization. Use when writing, editing, reviewing, or debugging synthesizable SystemC code for Intel SystemC Compiler (ICSC) and SingleSource library. Covers rules for module hierarchy, channels and ports, process declarations, reset behavior, sensitivity lists, SystemC and C++ data types and collections. Applies communication channels, memory modules, data types and utility functions from Single Source library.

Its SKILL.md is about 4.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Source-grounded notebooks. It works with C++. The repository describes itself as: This tool translates synthesizable SystemC code to synthesizable SystemVerilog.

When your agent uses it

Debugging synthesizable SystemC code for Intel SystemC Compiler (ICSC) and SingleSource library
Tasks that involve Source-grounded notebooks

Example prompts

“/systemc-tools”

Workflow steps

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

Identify the task type: implementation, refactor, debug, or review.
Read the nearby code first: module ports, constructor bindings, process declarations, sensitivity lists, reset logic, channel usage, and…
Check synthesis constraints before changing behavior: process kind, supported data types, control flow, function calls, dynamic…
Prefer existing project patterns over introducing new abstractions.
For edits, keep changes local to the relevant module, record, or helper.
Validate with the narrowest relevant test or build target. For CMake projects, use the CMake Tools build/test tools.
In reviews, lead with correctness, synthesis mismatch, reset/sensitivity, handshake, and missing-test risks.

What it can do on your machine

Read from SKILL.md and the folder at commit 68e56ae. 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
No scripts in the folder and no shell commands in SKILL.md.
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

Systemc Tools loads about 4.4k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 2,212 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~104
When it runs · the whole SKILL.md, loaded when a task matches: ~4.4k

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); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 2,212 words (~4,367 tokens).

“Use this skill for synthesizable SystemC code development and review in projects using ICSC and the SingleSource library. Apply it when implementing modules, records, channels, process code, assertions, or when reviewing existing code for synthesis, simulation, and SystemVerilog generation risks.”

— opening of SKILL.md by intel, Custom licence

name: systemc-tools
argument-hint: Describe the SystemC coding or review task and the files involved

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .github/skills/systemc-tools of intel/systemc-compiler.

Open the folder on GitHubat commit 68e56ae

Compare with similar skills

Systemc Tools 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.

Systemc Tools compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Systemc Tools this skillintel/systemc-compiler	320	—	~4.4k	Automated safety check: Pass	Custom licence	12 days ago
Qt C++ Code Reviewx-tools-author/x-tools	1.1k	2 repos	~4.3k	Automated safety check: Pass	BSD-3-Clause	5 days ago
YugabyteDB ASH Instrumentationyugabyte/yugabyte-db	11k	—	~4.5k	Automated safety check: Pass	Custom licence	today
pybind11 Release Preparationpybind/pybind11	18k	—	~1.7k	Automated safety check: Pass	Custom licence	today
Qt Cpp ReviewSerial-Studio/Serial-Studio	7.2k	—	~4.3k	Automated safety check: Pass	Custom licence	today
Paddle Eager GraphPaddlePaddle/Paddle	24k	—	~562	Automated safety check: Pass	Apache-2.0	8 days ago

Similar skills

Qt C++ Code Review
x-tools-author/x-tools
Read-only review of Qt6 C++ code that combines a deterministic lint script with six parallel analysis agents and reports only high-confidence issues.
1.1k GitHub starsUsed in 2 repos~4.3k tokens
DevelopmentAuto-check passed
YugabyteDB ASH Instrumentation
yugabyte/yugabyte-db
Procedure for adding or changing YugabyteDB Active Session History wait states in TServer and DocDB C++ code, including the macro to use for sync and async paths.
11k GitHub stars~4.5k tokensUpdated today
DevelopmentAuto-check passed
pybind11 Release Preparation
pybind/pybind11
Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.
18k GitHub stars~1.7k tokensUpdated today
DevelopmentAuto-check passed
Qt Cpp Review
Serial-Studio/Serial-Studio
Qt6/C++ deep code review for Serial Studio. An agent skill from Serial-Studio/Serial-Studio.
7.2k GitHub stars~4.3k tokensUpdated today
DevelopmentAuto-check passed
Paddle Eager Graph
PaddlePaddle/Paddle
A skill your agent uses when navigating Paddle eager-mode (dynamic graph) source code, tracing forward/backward execution, debugging autograd issues, understanding PyLayer, or investigating…
24k GitHub stars~562 tokensUpdated 8 days ago
DevelopmentAuto-check passed
ONNX Runtime Source Build
microsoft/onnxruntime
Official
Builds ONNX Runtime from source with its build scripts, explaining the update, build and test phases, key flags and where the build output lands.
22k GitHub stars~1.4k tokensUpdated today
DevelopmentAuto-check passed

Works with

Questions about Systemc Tools

What does Systemc Tools do?

A skill your agent uses when writing, editing, reviewing, or debugging synthesizable SystemC code for Intel SystemC Compiler (ICSC) and SingleSource library. Systemc Tools is an agent skill from intel/systemc-compiler, published by the product's own GitHub organization. Use when writing, editing, reviewing, or debugging synthesizable SystemC code for Intel SystemC Compiler (ICSC) and SingleSource library.

When should I use Systemc Tools?

Systemc Tools fits situations like: debugging synthesizable SystemC code for Intel SystemC Compiler (ICSC) and SingleSource library; tasks that involve Source-grounded notebooks.

How do I install Systemc Tools in Claude Code?

Run `npx skills add intel/systemc-compiler --skill systemc-tools -a claude-code`. Or copy the skill folder (.github/skills/systemc-tools in intel/systemc-compiler) into .claude/skills/systemc-tools in your project. Claude Code loads it when a task matches its description.

How do I install Systemc Tools in Codex?

Run `npx skills add intel/systemc-compiler --skill systemc-tools -a codex`. Or copy the skill folder (.github/skills/systemc-tools in intel/systemc-compiler) into .agents/skills/systemc-tools in your project. Codex loads it when a task matches its description.

Can I use Systemc Tools 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 intel/systemc-compiler --skill systemc-tools -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/systemc-tools, .gemini/skills/systemc-tools, .github/skills/systemc-tools and .opencode/skills/systemc-tools in your project.

What does Systemc Tools need to run?

SKILL.md names no scripts, command-line tools or credentials: Systemc Tools is instructions for the agent only.

Does Systemc Tools 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 Systemc Tools 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. Review the folder before installing.

What licence does Systemc Tools use?

Systemc Tools has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Systemc Tools use?

About 4.4k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Systemc Tools?

Skills that share tags, products or a category with Systemc Tools: Qt C++ Code Review (x-tools-author/x-tools, 1.1k stars), YugabyteDB ASH Instrumentation (yugabyte/yugabyte-db, 11k stars), pybind11 Release Preparation (pybind/pybind11, 18k stars) and Qt Cpp Review (Serial-Studio/Serial-Studio, 7.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Systemc Tools?

intel (a GitHub organization, an official publisher) maintains it in intel/systemc-compiler, which has 320 GitHub stars. The repository was last updated on September 25, 2026.

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

Install Systemc Tools

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

Qt C++ Code Review

YugabyteDB ASH Instrumentation

pybind11 Release Preparation

Qt Cpp Review

Paddle Eager Graph

ONNX Runtime Source Build

Related

Questions about Systemc Tools