New: 97,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

Build One Cc File

by apache in apache/impala

Build a single C++ file. An agent skill from apache/impala.

Apache-2.0Auto-check passed

Install Build One Cc File

skills CLI
$ npx skills add apache/impala --skill build-one-cc-file -a claude-code

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

GitHub CLI
$ gh skill install apache/impala build-one-cc-file --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/apache/impala.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/build-one-cc-file .claude/skills/build-one-cc-file && 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
build-one-cc-file
GitHub stars
1.3k
Token cost
~846 tokens
SKILL.md length
394 words
Files
2 (incl. scripts)
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

Build a single C++ file. An agent skill from apache/impala.

  • Works in 3 steps: Preflight and setup → First attempt MUST use dry-run → Execute real build after successful…
  • A single .cc file needs to be compiled to check for errors
  • SKILL.md covers Build One C++ File, Deterministic Rules, Available Scripts and Input Contract, plus 4 more sections
  • Runs Shell scripts from its folder

What it does

Build One Cc File is an agent skill from apache/impala. Build a single C++ file. Use when a single .cc file needs to be compiled to check for errors.

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/omake.sh`).

It works with C++. The licence is Apache-2.0.

When your agent uses it

  • A single .cc file needs to be compiled to check for errors

Example prompts

  • “/build-one-cc-file”

Requirements

  • A Bash shell

Workflow steps

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

  1. Preflight and setup
  2. First attempt MUST use dry-run
  3. Execute real build after successful dry-run

What it can do on your machine

Read from SKILL.md and the folder at commit bb537fb. 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/ (Shell), which the agent can run.

    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

Build One Cc File loads about 846 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 394 words of instructions outside code blocks.

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

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 apache/impala at commit bb537fb, republished under its Apache-2.0 licence (© apache). 394 words, ~846 tokens.

Download SKILL.mdSave it as .claude/skills/build-one-cc-file/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
build-one-cc-file
description
Build a single C++ file. Use when a single .cc file needs to be compiled to check for errors.
license
Apache-2.0
metadata.version
1.0

Build One C++ File

Use this skill when needing to compile one *.cc C++ file to check for errors. This provides a fast validation path without building the entire project.

Deterministic Rules

  • MUST run only from ${IMPALA_HOME}.
  • MUST configure the environment in the same shell session before building: export IMPALA_HOME=<git_repo_root> && cd "${IMPALA_HOME}" && source "${IMPALA_HOME}/bin/impala-config.sh" && source "${IMPALA_HOME}/bin/set-classpath.sh"
  • MUST use .agents/skills/build-one-cc-file/scripts/omake.sh as the only build command path.
  • MUST NOT use the agent's compile tool, Ninja, or direct CMake/Ninja invocation.

Available Scripts

  • .agents/skills/build-one-cc-file/scripts/omake.sh [--dry-run] <input> — builds the single object file for one C++ source.
    • Accepts a bare basename (rpc-trace).
    • --dry-run: prints the resolved make command on stdout and exits 0. Does not build.
    • Without --dry-run: runs the make command; exits 0 on success, non-zero on failure.
    • If no build target is found: exits non-zero (grep failure propagated via set -e).

Input Contract

Pass exactly one argument: the source basename only.

  • Input MUST be one token with no path separators.
  • Input MUST NOT include a directory path.
  • If input ends with .cc, strip .cc and continue.
  • Basename MUST match this pattern: [A-Za-z0-9_-]+
  • If validation fails, stop and request corrected input.

Examples:

  • Correct: .agents/skills/build-one-cc-file/scripts/omake.sh rpc-trace
  • Incorrect: .agents/skills/build-one-cc-file/scripts/omake.sh be/src/rpc/rpc-trace.cc
  • Incorrect: .agents/skills/build-one-cc-file/scripts/omake.sh rpc-trace.cc

If starting from a path like be/src/rpc/rpc-trace.cc, convert it to rpc-trace before invocation.

Execution Procedure

  1. Preflight and setup:
    • Ensure current directory is ${IMPALA_HOME}.
    • Ensure environment configuration has run in the current shell session.
  2. First attempt MUST use dry-run:
    • Run: .agents/skills/build-one-cc-file/scripts/omake.sh --dry-run <basename>
    • If dry-run fails, stop and report failure details.
  3. Execute real build after successful dry-run:
    • Run: .agents/skills/build-one-cc-file/scripts/omake.sh <basename>
Show full SKILL.md (136 more words)Show less

Ambiguity Handling

If basename collision occurs (multiple candidate source files map to the same basename), do not guess.

  • MUST ask the user to clarify which source path to use.
  • MUST wait for clarification before running the real build command.

Failure and Retry Policy

On any failure:

  • MUST report the exact command run.
  • MUST report exit code.
  • MUST report the first non-empty line from stderr; if stderr is empty, first stdout line containing "error:"

Retry behavior:

  • MUST analyze the failure first.
  • MUST attempt a concrete fix (for example corrected basename input or environment setup).
  • MAY retry the real build (step 3) once after analysis and fix attempt.
  • MUST NOT perform blind repeated retries.

Success Output Contract

On success, report:

  • Normalized basename used.
  • Dry-run command and result.
  • Real build command and result.
  • Final exit code and success confirmation.

© apache, Apache-2.0. 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 1 other file (scripts) in .agents/skills/build-one-cc-file of apache/impala.

  • SKILL.md
  • scripts/omake.sh

Open the folder on GitHubat commit bb537fb

Compare with similar skills

Build One Cc File 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.

Build One Cc File compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Build One Cc File this skillapache/impala1.3k—~846Automated safety check: PassApache-2.0
Paddle BuildPaddlePaddle/Paddle24k—~1kAutomated safety check: PassApache-2.0
Fory Releaseapache/fory4.6k—~2.9kAutomated safety check: PassApache-2.0
ONNX Runtime Shape Inference Safety Auditmicrosoft/onnxruntime22k—~3.3kAutomated safety check: PassMIT
Code Audit3stoneBrother/code-audit8931 repos~2.7kAutomated safety check: PassNone
Qt C++ Code Reviewx-tools-author/x-tools1.1k2 repos~4.3kAutomated safety check: PassBSD-3-Clause

Similar skills

  • Paddle Build

    PaddlePaddle/Paddle

    A skill your agent uses when needing to compile, rebuild, or install Paddle from source after code changes.

    24k GitHub stars~1k tokensUpdated 7 days ago
    AI & LLM EngineeringAuto-check passed

  • Fory Release

    apache/fory

    Prepare an Apache Fory release candidate from a clean release branch, including the version bump, RC tag, JVM staging, ASF source artifacts, SVN upload, and vote email.

    4.6k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • ONNX Runtime Shape Inference Safety Audit

    microsoft/onnxruntime

    Official

    Finds and fixes out-of-range output writes in ONNX Runtime operator shape-inference functions where a getNumOutputs guard admits too few outputs.

    22k GitHub stars~3.3k tokensUpdated today
    SecurityAuto-check passed

  • Code Audit

    3stoneBrother/code-audit

    Professional code security audit skill covering 55+ vulnerability types.

    893 GitHub starsUsed in 1 repo~2.7k tokens
    SecurityAuto-check passed

  • 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

  • Translation

    doxygen/doxygen

    Keeps all Doxygen and Doxywizard translations up to date across three mechanisms: translator C++ classes (src/translatorxx.h), Qt .ts locale files for the Doxywizard GUI (addon/doxywizard/i18n/)…

    6.6k GitHub stars~5.2k tokensUpdated 6 days ago
    Writing & ContentAuto-check passed

More from apache/impala

  • Git Fixup Push

    apache/impala

    Combines all git commits for a change into a single commit and pushes it to gerrit.

    1.3k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Questions about Build One Cc File

What does Build One Cc File do?

Build a single C++ file. An agent skill from apache/impala. Build One Cc File is an agent skill from apache/impala. Build a single C++ file.

When should I use Build One Cc File?

Build One Cc File fits situations like: A single .cc file needs to be compiled to check for errors.

How do I install Build One Cc File in Claude Code?

Run `npx skills add apache/impala --skill build-one-cc-file -a claude-code`. Or copy the skill folder (.agents/skills/build-one-cc-file in apache/impala) into .claude/skills/build-one-cc-file in your project. Claude Code loads it when a task matches its description.

How do I install Build One Cc File in Codex?

Run `npx skills add apache/impala --skill build-one-cc-file -a codex`. Or copy the skill folder (.agents/skills/build-one-cc-file in apache/impala) into .agents/skills/build-one-cc-file in your project. Codex loads it when a task matches its description.

Can I use Build One Cc File 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 apache/impala --skill build-one-cc-file -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/build-one-cc-file, .gemini/skills/build-one-cc-file, .github/skills/build-one-cc-file and .opencode/skills/build-one-cc-file in your project.

What does Build One Cc File need to run?

Going by SKILL.md and its folder, Build One Cc File needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Build One Cc File 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 Build One Cc File 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 Build One Cc File use?

Build One Cc File is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Build One Cc File use?

About 846 tokens (SKILL.md is roughly 3.4k 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 Build One Cc File?

Skills that share tags, products or a category with Build One Cc File: Paddle Build (PaddlePaddle/Paddle, 24k stars), Fory Release (apache/fory, 4.6k stars), ONNX Runtime Shape Inference Safety Audit (microsoft/onnxruntime, 22k stars) and Code Audit (3stoneBrother/code-audit, 893 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Build One Cc File?

apache (a GitHub organization) maintains it in apache/impala, which has 1,290 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.

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