Paddle Build
PaddlePaddle/Paddle
A skill your agent uses when needing to compile, rebuild, or install Paddle from source after code changes.
A skill your agent uses when: writing or reviewing C++, public headers, template function visibility, exported API ABI, ATFWUTILSYMBOLVISIBLE, or ATFWUTILFORCEINLINE.
MITAuto-check passed
Install Engineering Guidelines
$ npx skills add owent/libatbus --skill engineering-guidelines -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install owent/libatbus engineering-guidelines --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/owent/libatbus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/engineering-guidelines .claude/skills/engineering-guidelines && rm -rf skills-srcUse ~/.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/
Install the "engineering-guidelines" agent skill from https://github.com/owent/libatbus/tree/main/.agents/skills/engineering-guidelines into .claude/skills/engineering-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-guidelines", 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 install https://github.com/owent/libatbus/tree/main/.agents/skills/engineering-guidelinesType 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.
$ npx skills add owent/libatbus --skill engineering-guidelines -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install owent/libatbus engineering-guidelines --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/owent/libatbus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/engineering-guidelines .agents/skills/engineering-guidelines && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "engineering-guidelines" agent skill from https://github.com/owent/libatbus/tree/main/.agents/skills/engineering-guidelines into .agents/skills/engineering-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-guidelines", 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.
$ npx skills add owent/libatbus --skill engineering-guidelines -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install owent/libatbus engineering-guidelines --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/owent/libatbus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/engineering-guidelines .cursor/skills/engineering-guidelines && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "engineering-guidelines" agent skill from https://github.com/owent/libatbus/tree/main/.agents/skills/engineering-guidelines into .cursor/skills/engineering-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-guidelines", 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 https://github.com/owent/libatbus.git --path .agents/skills/engineering-guidelines--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add owent/libatbus --skill engineering-guidelines -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install owent/libatbus engineering-guidelines --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/owent/libatbus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/engineering-guidelines .gemini/skills/engineering-guidelines && rm -rf skills-srcUse ~/.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/
Install the "engineering-guidelines" agent skill from https://github.com/owent/libatbus/tree/main/.agents/skills/engineering-guidelines into .gemini/skills/engineering-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-guidelines", 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.
$ gh skill install owent/libatbus engineering-guidelinesInstalls 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).
$ npx skills add owent/libatbus --skill engineering-guidelines -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/owent/libatbus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/engineering-guidelines .github/skills/engineering-guidelines && rm -rf skills-srcUse ~/.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/
Install the "engineering-guidelines" agent skill from https://github.com/owent/libatbus/tree/main/.agents/skills/engineering-guidelines into .github/skills/engineering-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-guidelines", 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.
$ npx skills add owent/libatbus --skill engineering-guidelines -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install owent/libatbus engineering-guidelines --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/owent/libatbus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/engineering-guidelines .opencode/skills/engineering-guidelines && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "engineering-guidelines" agent skill from https://github.com/owent/libatbus/tree/main/.agents/skills/engineering-guidelines into .opencode/skills/engineering-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "engineering-guidelines", 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
engineering-guidelines- GitHub stars
- 234
- Token cost
- ~386 tokens
- SKILL.md length
- 181 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when: writing or reviewing C++, public headers, template function visibility, exported API ABI, ATFWUTILSYMBOLVISIBLE, or ATFWUTILFORCEINLINE.
- Template function visibility
- SKILL.md covers Header and ABI boundaries and Review and validation
- Calls git
- Exported API ABI
What it does
Engineering Guidelines is an agent skill from owent/libatbus. Use when: writing or reviewing C++, public headers, template function visibility, exported API ABI, ATFWUTILSYMBOLVISIBLE, or ATFWUTILFORCEINLINE.
Its SKILL.md is about 390 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with C++. The repository describes itself as: 用于搭建高性能、全异步、树形结构的BUS消息系统的跨平台框架库. The licence is MIT.
When your agent uses it
- Template function visibility
- Exported API ABI
- ATFWUTILSYMBOLVISIBLE
- ATFWUTILFORCEINLINE
Example prompts
- “/engineering-guidelines”
What it can do on your machine
Read from SKILL.md and the folder at commit d46c04d. 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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Engineering Guidelines loads about 386 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 181 words of instructions outside code blocks.
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
The full file from owent/libatbus at commit d46c04d, republished under its MIT licence (© owent). 181 words, ~386 tokens.
Download SKILL.mdSave it as
.claude/skills/engineering-guidelines/SKILL.md (or your agent's skills folder).- name
- engineering-guidelines
- description
- Use when: writing or reviewing C++, public headers, template function visibility, exported API ABI, ATFW_UTIL_SYMBOL_VISIBLE, or ATFW_UTIL_FORCEINLINE.
Engineering Guidelines
Use this skill before writing or reviewing C++ in libatbus.
Header and ABI boundaries
- Classify each interface as public library API or non-exported internal code before choosing a visibility marker.
- Every public non-template API must use
ATBUS_MACRO_API(or its matching*_APImacro) on the declaration or enclosing type, or useATFW_UTIL_FORCEINLINEfor a header definition. Plain/implicitinlineandconstexpralone do not satisfy this public-API rule. - A public template function defined in a header may instead use
ATFW_UTIL_SYMBOL_VISIBLE: a non-inlined instantiation can share one visible copy across linked targets, while an inlined call embeds a per-target copy. Keep the definition ODR-identical for every consumer so all copies have identical behavior. - Keep non-template implementations covered by an export macro in
.cppfiles by default. - Non-exported internal helpers may use ODR-correct implicit inline,
constexpr, or intentional plaininline.
Review and validation
- For touched public headers, verify the publication model, template visibility, and ODR-identical definition together.
- Preserve generated protocol code unless its source of truth is in scope.
- Run
clang-formatfor changed C++ files andgit diff --checkfor the scoped changes.
© owent, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/engineering-guidelines of owent/libatbus.
Open the folder on GitHubat commit d46c04d
Compare with similar skills
Engineering Guidelines 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Engineering Guidelines this skillowent/libatbus | 234 | — | ~386 | Automated safety check: Pass | MIT | |
| Paddle BuildPaddlePaddle/Paddle | 24k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| Fory Releaseapache/fory | 4.6k | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| ONNX Runtime Shape Inference Safety Auditmicrosoft/onnxruntime | 22k | — | ~3.3k | Automated safety check: Pass | MIT | |
| Code Audit3stoneBrother/code-audit | 893 | 1 repos | ~2.7k | Automated safety check: Pass | None | |
| Qt C++ Code Reviewx-tools-author/x-tools | 1.1k | 2 repos | ~4.3k | Automated safety check: Pass | BSD-3-Clause |
Similar skills
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.
- Official
ONNX Runtime Shape Inference Safety Audit
microsoft/onnxruntime
Finds and fixes out-of-range output writes in ONNX Runtime operator shape-inference functions where a getNumOutputs guard admits too few outputs.
Code Audit
3stoneBrother/code-audit
Professional code security audit skill covering 55+ vulnerability types.
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.
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/)…
More from owent/libatbus
Testing
owent/libatbus
A skill your agent uses when: designing, writing, reviewing, or running libatbus unit tests, filtering private-framework cases, testing topology/channel behavior, or diagnosing Windows test…
Libatbus Protocol Crypto
owent/libatbus
A skill your agent uses when: working on libatbus protocol transport, ECDH handshakes, cipher/compression negotiation, message framing, access token auth, connectioncontext, or crypto-related tests.
AI Agent Maintenance
owent/libatbus
A skill your agent uses when: initializing, auditing, or optimizing repository AI guidance, including AGENTS.md/CLAUDE.md bridges, Agent Skills, trigger descriptions, progressive disclosure, source…
Change Workflow
owent/libatbus
A skill your agent uses when: diagnosing or fixing a defect, test/build/runtime failure, or planning and implementing a nontrivial feature, behavior change, cross-module refactor, public API/ABI…
Shell Tooling
owent/libatbus
A skill your agent uses when: running terminal commands, writing or debugging shell/PowerShell scripts, choosing or installing CLI tools, or diagnosing command failures, quoting/escaping errors, or…
Related
Works with
Questions about Engineering Guidelines
What does Engineering Guidelines do?
A skill your agent uses when: writing or reviewing C++, public headers, template function visibility, exported API ABI, ATFWUTILSYMBOLVISIBLE, or ATFWUTILFORCEINLINE. Engineering Guidelines is an agent skill from owent/libatbus. Use when: writing or reviewing C++, public headers, template function visibility, exported API ABI, ATFWUTILSYMBOLVISIBLE, or ATFWUTILFORCEINLINE.
When should I use Engineering Guidelines?
Engineering Guidelines fits situations like: template function visibility; exported API ABI; ATFWUTILSYMBOLVISIBLE; ATFWUTILFORCEINLINE.
How do I install Engineering Guidelines in Claude Code?
Run `npx skills add owent/libatbus --skill engineering-guidelines -a claude-code`. Or copy the skill folder (.agents/skills/engineering-guidelines in owent/libatbus) into .claude/skills/engineering-guidelines in your project. Claude Code loads it when a task matches its description.
How do I install Engineering Guidelines in Codex?
Run `npx skills add owent/libatbus --skill engineering-guidelines -a codex`. Or copy the skill folder (.agents/skills/engineering-guidelines in owent/libatbus) into .agents/skills/engineering-guidelines in your project. Codex loads it when a task matches its description.
Can I use Engineering Guidelines 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 owent/libatbus --skill engineering-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/engineering-guidelines, .gemini/skills/engineering-guidelines, .github/skills/engineering-guidelines and .opencode/skills/engineering-guidelines in your project.
What does Engineering Guidelines need to run?
Going by SKILL.md and its folder, Engineering Guidelines needs the command-line tools its instructions call (git).
Does Engineering Guidelines access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Engineering Guidelines 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 Engineering Guidelines use?
Engineering Guidelines 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 Engineering Guidelines use?
About 386 tokens (SKILL.md is roughly 1.5k 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 Engineering Guidelines?
Skills that share tags, products or a category with Engineering Guidelines: 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 Engineering Guidelines?
owent (a GitHub user) maintains it in owent/libatbus, which has 234 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 11, 2026.
Source: owent/libatbus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.