Skip to content
Back to skills

Ls Trail Of Bits

ASecurity

Attribution-preserving wrapper for Trail of Bits security skills. Use

  • 6 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsgogitapisecurity

Works with

  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned November 7, 2026

npx -y skills add CruxExperts/LocalSetup --skill ls-trail-of-bits --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ls Trail Of Bits?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ls Trail Of Bits
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cruxexperts-ls-trail-of-bits/badge)](https://www.skillsdirectory.com/skills/cruxexperts-ls-trail-of-bits)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ls-trail-of-bits
description: Attribution-preserving wrapper for Trail of Bits security skills. Use
  when evaluating security review, audit, fuzzing, and vulnerability-analysis workflows.
metadata:
  version: '1.0'
extensions:
  external_skill:
    source_kind: wrapper
    source_url: https://github.com/trailofbits/skills
    source_path: .
    source_commit: cfe5d7b1619e47fb5b38b7e2561dad7e5f1e89af
    source_ref: main
    source_sha256: 6867b487caf10c73043a264b4bcc035f7fd943085b50545c7c0b0c996ad7fe57
    license: CC-BY-SA-4.0
    import_date: '2026-07-03'
    vetting_status: provenance-recorded-no-bundled-tooling-executed
---

# Trail Of Bits Security Skills

Use this skill when working on Trail of Bits security skills tasks.

## Workflow

- Do not copy CC-BY-SA-4.0 upstream content into LocalSetup skills without preserving attribution and share-alike obligations.
- Use the upstream bundle as a source map for security workflow gaps and route actual implementation through native skills when possible.
- Security tasks require explicit scope, authorization, and non-destructive validation boundaries.

## Boundaries

- Inspect the target repository before making changes.
- Prefer existing project patterns, declared package managers, and documented validation commands.
- Do not expose secrets, credentials, private user data, or production account identifiers in source, examples, or logs.
- When external APIs or current vendor behavior matter, verify against official docs before implementation.


## Upstream Coverage

See [upstream coverage](./references/upstream-coverage.md) for the compact inventory captured during this import wave.

## Provenance

- Source: `https://github.com/trailofbits/skills`
- Ref: `main` at `cfe5d7b1619e47fb5b38b7e2561dad7e5f1e89af`
- Source path: `.` (upstream repository root; the ordered manifest and aggregate recipe are in [upstream coverage](./references/upstream-coverage.md))
- License classification: `CC-BY-SA-4.0`; governing [upstream LICENSE](https://github.com/trailofbits/skills/blob/cfe5d7b1619e47fb5b38b7e2561dad7e5f1e89af/LICENSE)
- Source SHA-256: `6867b487caf10c73043a264b4bcc035f7fd943085b50545c7c0b0c996ad7fe57`

Files in this skill

  • SKILL.md2.1 KB
  • references/upstream-coverage.md11.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.