Fla Ascend Performance
fla-org/flash-linear-attention
Guidelines for Ascend NPU kernel / Triton-Ascend backend performance work in the FLA repo.
Extract bounded, deterministic evidence from crash and sanitizer logs, including signals, sanitizer classes, memory-safety indicators, stack-frame hashes, and source provenance, while reserving…
Install Analyze Crash Exploitability
$ npx skills add cyberful/cyberful --skill analyze-crash-exploitability -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cyberful/cyberful analyze-crash-exploitability --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/analyze-crash-exploitability .claude/skills/analyze-crash-exploitability && 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 "analyze-crash-exploitability" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/analyze-crash-exploitability into .claude/skills/analyze-crash-exploitability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-crash-exploitability", 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/analyze-crash-exploitabilityType 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 analyze-crash-exploitability -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cyberful/cyberful analyze-crash-exploitability --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/analyze-crash-exploitability .agents/skills/analyze-crash-exploitability && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analyze-crash-exploitability" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/analyze-crash-exploitability into .agents/skills/analyze-crash-exploitability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-crash-exploitability", 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 analyze-crash-exploitability -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cyberful/cyberful analyze-crash-exploitability --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/analyze-crash-exploitability .cursor/skills/analyze-crash-exploitability && 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 "analyze-crash-exploitability" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/analyze-crash-exploitability into .cursor/skills/analyze-crash-exploitability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-crash-exploitability", 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/analyze-crash-exploitability--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 analyze-crash-exploitability -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cyberful/cyberful analyze-crash-exploitability --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/analyze-crash-exploitability .gemini/skills/analyze-crash-exploitability && 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 "analyze-crash-exploitability" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/analyze-crash-exploitability into .gemini/skills/analyze-crash-exploitability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-crash-exploitability", 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 analyze-crash-exploitabilityInstalls 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 analyze-crash-exploitability -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/analyze-crash-exploitability .github/skills/analyze-crash-exploitability && 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 "analyze-crash-exploitability" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/analyze-crash-exploitability into .github/skills/analyze-crash-exploitability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-crash-exploitability", 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 analyze-crash-exploitability -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 analyze-crash-exploitability --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/analyze-crash-exploitability .opencode/skills/analyze-crash-exploitability && 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 "analyze-crash-exploitability" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/analyze-crash-exploitability into .opencode/skills/analyze-crash-exploitability/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analyze-crash-exploitability", 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
analyze-crash-exploitability- GitHub stars
- 135
- Token cost
- ~563 tokens
- SKILL.md length
- 153 words
- Files
- 9 (incl. scripts, references, assets)
- Skills in repo
- 85
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Extract bounded, deterministic evidence from crash and sanitizer logs, including signals, sanitizer classes, memory-safety indicators, stack-frame hashes, and source provenance, while reserving…
- Security work in your project
- SKILL.md covers Extract reproducible evidence and Decide manually
- Runs Python scripts from its folder
What it does
Analyze Crash Exploitability is an agent skill from cyberful/cyberful. Extract bounded, deterministic evidence from crash and sanitizer logs, including signals, sanitizer classes, memory-safety indicators, stack-frame hashes, and source provenance, while reserving exploitability judgment for manual analysis.
Its SKILL.md is about 560 tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including scripts, reference files and assets (for example `agents/openai.yaml`, `assets/crash-analysis.example.json` and `assets/crash-analysis.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
- Security work in your project
Example prompts
- “/analyze-crash-exploitability”
Requirements
- Python 3
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
Ships 2 files in scripts/ (Python), 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
Analyze Crash Exploitability loads about 563 tokens when it runs, and up to ~856 if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 153 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); the scripts in this folder are not scanned.
SKILL.md
The full file from cyberful/cyberful at commit ec598a6, republished under its AGPL-3.0 licence (© cyberful). 153 words, ~563 tokens.
Download SKILL.mdSave it as
.claude/skills/analyze-crash-exploitability/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- analyze-crash-exploitability
- description
- Extract bounded, deterministic evidence from crash and sanitizer logs, including signals, sanitizer classes, memory-safety indicators, stack-frame hashes, and source provenance, while reserving exploitability judgment for manual analysis.
- metadata.domain
- evidence-analysis
- metadata.subdomain
- crash-analysis
- metadata.triggers
- analyze crash exploitability, inspect sanitizer crash log, triage memory safety crash, crash evidence analysis, stack trace fingerprinting, reproduce crash…
- metadata.tags
- crash, exploitability, sanitizer, memory-safety, stack-trace, offline-analysis
Analyze Crash Exploitability
Use the analyzer to normalize crash evidence, not to label a crash exploitable. Exploitability depends on attacker control, reachable state, mitigations, allocator behavior, process privilege, and reliable influence over control or sensitive data.
Extract reproducible evidence
Read references/crash-evidence-method.md. Stage scripts/analyze_crash_exploitability.py, assets/crash-analysis.example.json, and assets/crash-analysis.schema.json. The script snapshots confined regular text logs and emits bounded indicators, sanitizer and signal classes, hashed normalized frames, and source digests under assets/crash-evidence.schema.json.
Evidence indicators are literal matches in supplied logs. They can prioritize reproduction and debugging but cannot establish attacker control, primitive quality, or exploit reliability. Preserve build identity, input digest, runtime arguments, environment, mitigations, and the unmodified crash artifact separately.
Decide manually
Reproduce under the same and hardened builds, determine the faulting operation and controlled bytes, trace lifetime and bounds, assess read/write/control effects, and test relevant mitigations. Report the smallest supported primitive and uncertainty, never a score inferred only from a signal or sanitizer label.
© 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 8 other files (scripts, references, assets) in cyberful/builtin/skills/analyze-crash-exploitability of cyberful/cyberful.
- SKILL.md
- agents/openai.yaml
- assets/crash-analysis.example.json
- assets/crash-analysis.schema.json
- assets/crash-evidence.schema.json
- references/crash-evidence-method.md
- scripts/analyze_crash_exploitability.py
- scripts/manifest.json
- tests/test_analyze_crash_exploitability.py
Open the folder on GitHubat commit ec598a6
Compare with similar skills
Analyze Crash Exploitability 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 |
|---|---|---|---|---|---|---|
| Analyze Crash Exploitability this skillcyberful/cyberful | 135 | — | ~563 | 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 Analyze Crash Exploitability
What does Analyze Crash Exploitability do?
Extract bounded, deterministic evidence from crash and sanitizer logs, including signals, sanitizer classes, memory-safety indicators, stack-frame hashes, and source provenance, while reserving…. Analyze Crash Exploitability is an agent skill from cyberful/cyberful. Extract bounded, deterministic evidence from crash and sanitizer logs, including signals, sanitizer classes, memory-safety indicators, stack-frame hashes, and source provenance, while reserving exploitability judgment for manual analysis.
When should I use Analyze Crash Exploitability?
Analyze Crash Exploitability fits situations like: security work in your project.
How do I install Analyze Crash Exploitability in Claude Code?
Run `npx skills add cyberful/cyberful --skill analyze-crash-exploitability -a claude-code`. Or copy the skill folder (cyberful/builtin/skills/analyze-crash-exploitability in cyberful/cyberful) into .claude/skills/analyze-crash-exploitability in your project. Claude Code loads it when a task matches its description.
How do I install Analyze Crash Exploitability in Codex?
Run `npx skills add cyberful/cyberful --skill analyze-crash-exploitability -a codex`. Or copy the skill folder (cyberful/builtin/skills/analyze-crash-exploitability in cyberful/cyberful) into .agents/skills/analyze-crash-exploitability in your project. Codex loads it when a task matches its description.
Can I use Analyze Crash Exploitability 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 analyze-crash-exploitability -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analyze-crash-exploitability, .gemini/skills/analyze-crash-exploitability, .github/skills/analyze-crash-exploitability and .opencode/skills/analyze-crash-exploitability in your project.
What does Analyze Crash Exploitability need to run?
Going by SKILL.md and its folder, Analyze Crash Exploitability needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Analyze Crash Exploitability 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 Analyze Crash Exploitability 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 Analyze Crash Exploitability use?
Analyze Crash Exploitability 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 Analyze Crash Exploitability use?
About 563 tokens (SKILL.md is roughly 2.3k 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 293 tokens, read only when the agent opens those files.
What are the alternatives to Analyze Crash Exploitability?
Skills that share tags, products or a category with Analyze Crash Exploitability: 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 Analyze Crash Exploitability?
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.