Fla Ascend Performance
fla-org/flash-linear-attention
Guidelines for Ascend NPU kernel / Triton-Ascend backend performance work in the FLA repo.
Trace uploaded, imported, generated, archived, converted, scanned, rendered, and downloaded files across storage, naming, extraction, parser, sandbox, and cleanup boundaries.
Install Trace File Processing Pipelines
$ npx skills add cyberful/cyberful --skill trace-file-processing-pipelines -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cyberful/cyberful trace-file-processing-pipelines --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/cyberful/cyberful.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cyberful/builtin/skills/trace-file-processing-pipelines .claude/skills/trace-file-processing-pipelines && 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 "trace-file-processing-pipelines" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/trace-file-processing-pipelines into .claude/skills/trace-file-processing-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-file-processing-pipelines", 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/cyberful/cyberful/tree/main/cyberful/builtin/skills/trace-file-processing-pipelinesType 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 cyberful/cyberful --skill trace-file-processing-pipelines -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cyberful/cyberful trace-file-processing-pipelines --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cyberful/builtin/skills/trace-file-processing-pipelines .agents/skills/trace-file-processing-pipelines && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "trace-file-processing-pipelines" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/trace-file-processing-pipelines into .agents/skills/trace-file-processing-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-file-processing-pipelines", 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 cyberful/cyberful --skill trace-file-processing-pipelines -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cyberful/cyberful trace-file-processing-pipelines --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cyberful/builtin/skills/trace-file-processing-pipelines .cursor/skills/trace-file-processing-pipelines && 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 "trace-file-processing-pipelines" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/trace-file-processing-pipelines into .cursor/skills/trace-file-processing-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-file-processing-pipelines", 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/cyberful/cyberful.git --path cyberful/builtin/skills/trace-file-processing-pipelines--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 cyberful/cyberful --skill trace-file-processing-pipelines -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cyberful/cyberful trace-file-processing-pipelines --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cyberful/builtin/skills/trace-file-processing-pipelines .gemini/skills/trace-file-processing-pipelines && 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 "trace-file-processing-pipelines" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/trace-file-processing-pipelines into .gemini/skills/trace-file-processing-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-file-processing-pipelines", 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 cyberful/cyberful trace-file-processing-pipelinesInstalls 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 cyberful/cyberful --skill trace-file-processing-pipelines -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .github/skills && cp -r skills-src/cyberful/builtin/skills/trace-file-processing-pipelines .github/skills/trace-file-processing-pipelines && 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 "trace-file-processing-pipelines" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/trace-file-processing-pipelines into .github/skills/trace-file-processing-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-file-processing-pipelines", 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 cyberful/cyberful --skill trace-file-processing-pipelines -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cyberful/cyberful trace-file-processing-pipelines --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cyberful/builtin/skills/trace-file-processing-pipelines .opencode/skills/trace-file-processing-pipelines && 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 "trace-file-processing-pipelines" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/trace-file-processing-pipelines into .opencode/skills/trace-file-processing-pipelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-file-processing-pipelines", 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
trace-file-processing-pipelines- GitHub stars
- 135
- Token cost
- ~646 tokens
- SKILL.md length
- 176 words
- Files
- 5 (incl. references, assets)
- Skills in repo
- 85
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Trace uploaded, imported, generated, archived, converted, scanned, rendered, and downloaded files across storage, naming, extraction, parser, sandbox, and cleanup boundaries.
- Prove path resolution
- SKILL.md covers Construct the pipeline, Validate with bounded fixtures and Confirmation standard
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Derived-artifact
What it does
Trace File Processing Pipelines is an agent skill from cyberful/cyberful. Trace uploaded, imported, generated, archived, converted, scanned, rendered, and downloaded files across storage, naming, extraction, parser, sandbox, and cleanup boundaries. Use to prove path resolution, active-content, parser-chain, derived-artifact, isolation, or lifecycle failures without duplicating deserialization or XML specialist procedures.
Its SKILL.md is about 650 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `agents/openai.yaml`, `assets/file-processing-ledger.example.json` and `assets/file-processing-ledger.schema.json`).
It sits in Security. The repository describes itself as: Cyberful is an open-source AI Red Team for discovering, exploiting, verifying, and remediating vulnerabilities. The licence is AGPL-3.0.
When your agent uses it
- Prove path resolution
- Derived-artifact
- Lifecycle failures without duplicating deserialization
- XML specialist procedures
Example prompts
- “/trace-file-processing-pipelines”
What it can do on your machine
Read from SKILL.md and the folder at commit ec598a6. 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
Trace File Processing Pipelines loads about 646 tokens when it runs, and up to ~931 if it reads all its reference files. Until then it costs about 96 tokens; SKILL.md has 176 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 cyberful/cyberful at commit ec598a6, republished under its AGPL-3.0 licence (© cyberful). 176 words, ~646 tokens.
Download SKILL.mdSave it as
.claude/skills/trace-file-processing-pipelines/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- trace-file-processing-pipelines
- description
- Trace uploaded, imported, generated, archived, converted, scanned, rendered, and downloaded files across storage, naming, extraction, parser, sandbox, and cleanup boundaries. Use to prove path resolution, active-content, parser-chain, derived-artifact, isolation, or lifecycle failures without duplicating deserialization or XML specialist procedures.
- metadata.domain
- application-security
- metadata.subdomain
- file-processing-pipelines
- metadata.triggers
- file processing pipeline, upload transformation trace, archive extraction path, document conversion security, derived file exposure, parser sandbox boundary
- metadata.tags
- file-upload, archive, conversion, path-resolution, parser-isolation, lifecycle
Trace File Processing Pipelines
Follow one controlled artifact from acceptance to every terminal consumer. Extension or MIME acceptance is not the conclusion; establish which bytes each downstream component actually reads, resolves, transforms, writes, fetches, renders, or executes.
Construct the pipeline
Start from assets/file-processing-ledger.example.json and retain the contract in assets/file-processing-ledger.schema.json. Record original hash, uploader authority, metadata, storage identifier, canonical path, queue or job identity, scanners, extractors, converters, renderers, derived objects, download policy, retention, and deletion propagation.
Read references/pipeline-invariants.md for boundary-specific questions. Invoke test-deserialization-object-binding when a stage reconstructs language or native objects, and test-soap-xml-services when XML processing is decisive.
Validate with bounded fixtures
Use inert marker files, tiny archives, controlled names, matched metadata, and explicit resource ceilings. Compare original and derived hashes, canonical paths, execution identity, network reach, filesystem reach, and cleanup. Stop before leaving authorized storage or causing parser instability.
Confirmation standard
Report the accepting interface, exact stage and component, attacker-controlled property, failed invariant, canonical path or derived artifact, matched control, security effect, cleanup behavior, and affected authority. A parser error or accepted upload alone is insufficient.
© cyberful, AGPL-3.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 4 other files (references, assets) in cyberful/builtin/skills/trace-file-processing-pipelines of cyberful/cyberful.
- SKILL.md
- agents/openai.yaml
- assets/file-processing-ledger.example.json
- assets/file-processing-ledger.schema.json
- references/pipeline-invariants.md
Open the folder on GitHubat commit ec598a6
Compare with similar skills
Trace File Processing Pipelines 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 |
|---|---|---|---|---|---|---|
| Trace File Processing Pipelines this skillcyberful/cyberful | 135 | — | ~646 | Automated safety check: Pass | AGPL-3.0 | |
| Fla Ascend Performancefla-org/flash-linear-attention | 5.8k | — | ~6.3k | Automated safety check: Pass | MIT | |
| Deepsec Documentation Guidevercel-labs/deepsec | 8.1k | — | ~956 | Automated safety check: Pass | Apache-2.0 | |
| Skill Scannergetsentry/skills | 1k | 4 repos | ~2.5k | Automated safety check: Warn | Apache-2.0 | |
| Serenity Aleabitoreddityan-labs/serenity-aleabitoreddit | 480 | 1 repos | ~3.3k | Automated safety check: Pass | None | |
| Security Alert Triageelastic/agent-skills | 592 | 1 repos | ~3.5k | Automated safety check: Notes | Apache-2.0 |
Similar skills
- Official
Deepsec Documentation Guide
vercel-labs/deepsec
Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.
- Official
Skill Scanner
getsentry/skills
Scan agent skills for security issues. An agent skill from getsentry/skills.
Serenity Aleabitoreddit
yan-labs/serenity-aleabitoreddit
Apply trader Serenity's (@aleabitoreddit) AI/semiconductor supply-chain analytical lens to US-stock ideas and market judgment.
- Official
Security Alert Triage
elastic/agent-skills
Triage Elastic Security alerts — gather context, classify threats, create cases, and acknowledge.
Shiro Attack CLI
SummerSec/ShiroAttack2
当用户要求利用、检测或测试 Apache Shiro rememberMe 反序列化漏洞 (Shiro-550, CVE-2016-4437) 时使用。触发词包括 "Shiro"、"rememberMe"、"shiro attack"、"CVE-2016-4437"、"Shiro-550"、"爆破 Shiro key"、"利用 Shiro"、"Shiro…
More from cyberful/cyberful
All 85 skills in this repoAudit Infrastructure As Code
cyberful/cyberful
Audit infrastructure-as-code artifacts for unsafe defaults, policy gaps, privilege exposure, control drift, and deployment-impact evidence.
Audit Kubernetes Policy Enforcement
cyberful/cyberful
Audit Kubernetes admission and policy-as-code enforcement against local workload manifests, exception paths, namespace scope, and deployment evidence.
Audit Pci Dss Penetration Test Evidence
cyberful/cyberful
Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence.
Operate Content Discovery
cyberful/cyberful
Design and interpret advanced content discovery with ffuf and complementary web fuzzers.
Operate Network Recon
cyberful/cyberful
Build a high-fidelity network and service inventory using Nmap, Masscan, packet capture, DNS, and protocol-specific follow-up.
Operate Sast Toolchain
cyberful/cyberful
Operate Semgrep and source-oriented static analysis as a hypothesis, coverage, and regression system during advanced code audits.
Related
Categories
Questions about Trace File Processing Pipelines
What does Trace File Processing Pipelines do?
Trace uploaded, imported, generated, archived, converted, scanned, rendered, and downloaded files across storage, naming, extraction, parser, sandbox, and cleanup boundaries. Trace File Processing Pipelines is an agent skill from cyberful/cyberful. Trace uploaded, imported, generated, archived, converted, scanned, rendered, and downloaded files across storage, naming, extraction, parser, sandbox, and cleanup boundaries.
When should I use Trace File Processing Pipelines?
Trace File Processing Pipelines fits situations like: prove path resolution; derived-artifact; lifecycle failures without duplicating deserialization; XML specialist procedures.
How do I install Trace File Processing Pipelines in Claude Code?
Run `npx skills add cyberful/cyberful --skill trace-file-processing-pipelines -a claude-code`. Or copy the skill folder (cyberful/builtin/skills/trace-file-processing-pipelines in cyberful/cyberful) into .claude/skills/trace-file-processing-pipelines in your project. Claude Code loads it when a task matches its description.
How do I install Trace File Processing Pipelines in Codex?
Run `npx skills add cyberful/cyberful --skill trace-file-processing-pipelines -a codex`. Or copy the skill folder (cyberful/builtin/skills/trace-file-processing-pipelines in cyberful/cyberful) into .agents/skills/trace-file-processing-pipelines in your project. Codex loads it when a task matches its description.
Can I use Trace File Processing Pipelines 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 cyberful/cyberful --skill trace-file-processing-pipelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/trace-file-processing-pipelines, .gemini/skills/trace-file-processing-pipelines, .github/skills/trace-file-processing-pipelines and .opencode/skills/trace-file-processing-pipelines in your project.
What does Trace File Processing Pipelines need to run?
SKILL.md names no scripts, command-line tools or credentials: Trace File Processing Pipelines is instructions for the agent only.
Does Trace File Processing Pipelines 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 Trace File Processing Pipelines 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 Trace File Processing Pipelines use?
Trace File Processing Pipelines is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Trace File Processing Pipelines use?
About 646 tokens (SKILL.md is roughly 2.6k 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 285 tokens, read only when the agent opens those files.
What are the alternatives to Trace File Processing Pipelines?
Skills that share tags, products or a category with Trace File Processing Pipelines: Fla Ascend Performance (fla-org/flash-linear-attention, 5.8k stars), Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars), Skill Scanner (getsentry/skills, 1k stars) and Serenity Aleabitoreddit (yan-labs/serenity-aleabitoreddit, 480 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Trace File Processing Pipelines?
cyberful (a GitHub organization) maintains it in cyberful/cyberful, which has 135 GitHub stars. The repository holds 85 skills in this directory. The repository was last updated on August 24, 2026.
Source: cyberful/cyberful on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.