admin/trailofbits-skills-curated
1
0
Fork 0
mirror of https://github.com/trailofbits/skills-curated synced 2026-06-21 14:12:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

Initial skills-curated marketplace infrastructure

Browse Source 
Curated, community-vetted Claude Code plugin marketplace with CI checks
mirroring trailofbits/skills: ruff, shellcheck, shfmt, bats linting plus
JSON validation, marketplace consistency, frontmatter, hardcoded path,
and personal email checks. Includes ask-questions-if-underspecified as
seed plugin.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Dan Guido
2026-02-06 10:59:09 -05:00
commit 5988966e3a
15 changed files with 1224 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.claude-plugin/marketplace.json
+24
View File
@@ -0,0 +1,24 @@
{
"name": "skills-curated",
"owner": {
"name": "Trail of Bits",
"email": "opensource@trailofbits.com"
},
"metadata": {
"version": "1.0.0",
"description": "Curated, community-vetted Claude Code plugins reviewed for quality and safety"
},
"plugins": [
{
"name": "ask-questions-if-underspecified",
"version": "1.0.1",
"description": "Clarify requirements before implementing. When doubting, ask questions.",
"author": {
"name": "Kevin Valerio",
"email": "opensource@trailofbits.com",
"url": "https://github.com/trailofbits"
},
"source": "./plugins/ask-questions-if-underspecified"
}
]
}
.github/ISSUE_TEMPLATE/trophy-case.yml
+42
View File
@@ -0,0 +1,42 @@
name: Trophy Case Submission
description: Found a bug using one of our skills? Add it to the trophy case!
title: "[Trophy] "
labels: ["trophy-case"]
body:
- type: markdown
attributes:
value: |
Thanks for sharing your find! We love seeing these skills help discover real bugs.
- type: input
id: bug-link
attributes:
label: Bug Link
description: Link to the bug report, PR, advisory, or writeup
placeholder: https://github.com/org/repo/issues/123
validations:
required: true
- type: input
id: skill
attributes:
label: Skill Used
description: Which skill helped you find it?
placeholder: constant-time-analysis
validations:
required: true
- type: input
id: title
attributes:
label: Bug Title
description: Short description of the vulnerability (this will be the link text in the trophy case table)
placeholder: Timing side-channel in ECDSA verification
validations:
required: true
- type: textarea
id: context
attributes:
label: Additional Context (optional)
description: Anything else you'd like to share about the find?
.github/dependabot.yml
+21
View File
@@ -0,0 +1,21 @@
version: 2
updates:
- package-ecosystem: pip
directory: /
schedule:
interval: weekly
cooldown:
default-days: 7
groups:
all:
patterns: ["*"]
- package-ecosystem: github-actions
directory: /
schedule:
interval: weekly
cooldown:
default-days: 7
groups:
all:
patterns: ["*"]
.github/workflows/lint.yml
+87
View File
@@ -0,0 +1,87 @@
name: Lint
on:
push:
branches: [main]
pull_request:
branches: [main]
permissions:
contents: read
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
jobs:
ruff:
name: Python (ruff)
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
persist-credentials: false
- uses: astral-sh/ruff-action@57714a7c8a2e59f32539362ba31877a1957dded1 # v3.5.1
with:
args: check --output-format=github
- uses: astral-sh/ruff-action@57714a7c8a2e59f32539362ba31877a1957dded1 # v3.5.1
with:
args: format --check
shellcheck:
name: Shell (shellcheck)
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
persist-credentials: false
- name: Run shellcheck
run: |
shfiles=$(find plugins -name "*.sh" -type f 2>/dev/null)
if [ -n "$shfiles" ]; then
echo "$shfiles" | xargs shellcheck -x
else
echo "No shell scripts found, skipping"
fi
shfmt:
name: Shell (shfmt)
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
persist-credentials: false
- name: Install shfmt
run: |
curl -sS https://webinstall.dev/shfmt | bash
echo "$HOME/.local/bin" >> "$GITHUB_PATH"
- name: Run shfmt
run: |
shfiles=$(find plugins -name "*.sh" -type f 2>/dev/null)
if [ -n "$shfiles" ]; then
echo "$shfiles" | xargs shfmt -i 2 -ci -d
else
echo "No shell scripts found, skipping"
fi
bats:
name: Shell (bats)
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
persist-credentials: false
- name: Install bats and uv
run: |
sudo apt-get update
sudo apt-get install -y bats
curl -LsSf https://astral.sh/uv/install.sh | sh
echo "$HOME/.local/bin" >> "$GITHUB_PATH"
- name: Run hook tests
run: |
batfiles=$(find plugins -name "*.bats" -type f 2>/dev/null)
if [ -n "$batfiles" ]; then
echo "$batfiles" | xargs bats
else
echo "No bats test files found, skipping"
fi
.github/workflows/validate.yml
+130
View File
@@ -0,0 +1,130 @@
name: Validate
on:
push:
branches: [main]
pull_request:
branches: [main]
permissions:
contents: read
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
cancel-in-progress: true
jobs:
validate:
name: Validate plugins and skills
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
with:
persist-credentials: false
- name: Validate JSON files
run: |
echo "Validating marketplace.json..."
python3 -m json.tool .claude-plugin/marketplace.json > /dev/null
echo "Validating plugin.json files..."
for f in plugins/*/.claude-plugin/plugin.json; do
echo " Checking $f"
python3 -m json.tool "$f" > /dev/null
done
- name: Check marketplace consistency
run: |
echo "Checking all marketplace plugins have directories..."
python3 -c "
import json
import os
import sys
with open('.claude-plugin/marketplace.json') as f:
marketplace = json.load(f)
errors = []
for plugin in marketplace['plugins']:
name = plugin['name']
source = plugin['source']
# source is like ./plugins/name
path = source.lstrip('./')
if not os.path.isdir(path):
errors.append(f'Plugin {name}: directory {path} not found')
plugin_json = os.path.join(path, '.claude-plugin', 'plugin.json')
if not os.path.isfile(plugin_json):
errors.append(f'Plugin {name}: missing {plugin_json}')
if errors:
for e in errors:
print(f'ERROR: {e}', file=sys.stderr)
sys.exit(1)
print(f'All {len(marketplace[\"plugins\"])} plugins validated')
"
- name: Validate SKILL.md frontmatter
run: |
echo "Checking SKILL.md frontmatter..."
python3 -c "
import os
import re
import sys
errors = []
skill_count = 0
for root, dirs, files in os.walk('plugins'):
for f in files:
if f == 'SKILL.md':
path = os.path.join(root, f)
skill_count += 1
with open(path) as fp:
content = fp.read()
# Check for frontmatter
if not content.startswith('---'):
errors.append(f'{path}: missing YAML frontmatter')
continue
# Extract frontmatter
match = re.match(r'^---\n(.*?)\n---', content, re.DOTALL)
if not match:
errors.append(f'{path}: malformed frontmatter')
continue
frontmatter = match.group(1)
# Check for required fields
if 'name:' not in frontmatter:
errors.append(f'{path}: missing \"name\" in frontmatter')
if 'description:' not in frontmatter:
errors.append(f'{path}: missing \"description\" in frontmatter')
if errors:
for e in errors:
print(f'ERROR: {e}', file=sys.stderr)
sys.exit(1)
print(f'All {skill_count} SKILL.md files have valid frontmatter')
"
- name: Check for hardcoded paths
run: |
echo "Checking for hardcoded user paths..."
if grep -rE '/home/[a-z]|/Users/[A-Z]' plugins/ --include='*.md' --include='*.py' --include='*.json' | grep -v '/path/to'; then
echo "ERROR: Found hardcoded user paths (see above)"
exit 1
fi
echo "No hardcoded user paths found"
- name: Check for personal emails
run: |
echo "Checking for personal emails..."
if grep -r '@trailofbits.com' . --include='*.json' --include='*.toml' | grep -v 'opensource@trailofbits.com' | grep -v '.git'; then
echo "ERROR: Found personal emails (should use opensource@trailofbits.com)"
exit 1
fi
echo "No personal emails found"
.gitignore
+33
View File
@@ -0,0 +1,33 @@
# macOS
.DS_Store
.AppleDouble
.LSOverride
# Python
__pycache__/
*.py[cod]
*$py.class
*.so
.Python
.venv/
venv/
ENV/
.uv/
# IDE
.idea/
.vscode/
*.swp
*.swo
*~
# Build artifacts
dist/
build/
*.egg-info/
# Local plugin cache
.claude/
# MCP server config (contains API keys)
.mcp.json
.pre-commit-config.yaml
+31
View File
@@ -0,0 +1,31 @@
repos:
- repo: https://github.com/astral-sh/ruff-pre-commit
rev: v0.14.13
hooks:
- id: ruff-check
args: [--fix, --exit-non-zero-on-fix]
- id: ruff-format
- repo: local
hooks:
- id: shellcheck
name: shellcheck
entry: shellcheck
args: [-x]
language: system
types: [shell]
- repo: https://github.com/scop/pre-commit-shfmt
rev: v3.12.0-2
hooks:
- id: shfmt
args: [-i, "2", -ci, --write]
- repo: https://github.com/pre-commit/pre-commit-hooks
rev: v6.0.0
hooks:
- id: check-yaml
args: [--unsafe]
- id: check-json
- id: end-of-file-fixer
- id: trailing-whitespace
CLAUDE.md
+226
View File
@@ -0,0 +1,226 @@
# Contributing Skills
## Resources
**Official Anthropic documentation (always check these first):**
- [Claude Code Plugins](https://docs.anthropic.com/en/docs/claude-code/plugins)
- [Agent Skills](https://docs.anthropic.com/en/docs/claude-code/skills)
- [Best Practices](https://docs.anthropic.com/en/docs/claude-code/skills#best-practices)
**Reference skills** - learn by example at different complexity levels:
| Complexity | Skill | What It Demonstrates |
|------------|-------|---------------------|
| **Basic** | [ask-questions-if-underspecified](plugins/ask-questions-if-underspecified/) | Minimal frontmatter, simple guidance |
| **Intermediate** | [constant-time-analysis](https://github.com/trailofbits/skills/tree/main/plugins/constant-time-analysis) | Python package, references/, language-specific docs |
| **Advanced** | [culture-index](https://github.com/trailofbits/skills/tree/main/plugins/culture-index) | Scripts, workflows/, templates/, PDF extraction, multiple entry points |
**When in doubt, copy one of these and adapt it.**
**Deep dives on skill authoring:**
- [Claude Skills Deep Dive](https://leehanchung.github.io/blogs/2025/10/26/claude-skills-deep-dive/) - Comprehensive analysis of skill architecture
- [Claude Code Skills Training](https://huggingface.co/blog/sionic-ai/claude-code-skills-training) - Practical authoring guide
**Example plugins worth studying:**
- [trailofbits/skills](https://github.com/trailofbits/skills) - The original Trail of Bits skills marketplace
- [superpowers](https://github.com/obra/superpowers) - Advanced workflow patterns, TDD enforcement, multi-skill orchestration
- [compound-engineering-plugin](https://github.com/EveryInc/compound-engineering-plugin) - Production plugin structure
**For Claude:** Use the `claude-code-guide` subagent for plugin/skill questions - it has access to official documentation.
## Technical Reference
### Plugin Structure
```
plugins/
<plugin-name>/
.claude-plugin/
plugin.json # Plugin metadata (name, version, description, author)
commands/ # Optional: slash commands
agents/ # Optional: autonomous agents
skills/ # Optional: knowledge/guidance
<skill-name>/
SKILL.md # Entry point with frontmatter
references/ # Optional: detailed docs
workflows/ # Optional: step-by-step guides
scripts/ # Optional: utility scripts
hooks/ # Optional: event hooks
README.md # Plugin documentation
```
**Important**: Component directories (`skills/`, `commands/`, `agents/`, `hooks/`) must be at the plugin root, NOT inside `.claude-plugin/`. Only `plugin.json` belongs in `.claude-plugin/`.
### Frontmatter
```yaml
---
name: skill-name # kebab-case, max 64 chars
description: "Third-person description of what it does and when to use it"
allowed-tools: # Optional: restrict to needed tools only
- Read
- Grep
---
```
### Naming Conventions
- **kebab-case**: `constant-time-analysis`, not `constantTimeAnalysis`
- **Gerund form preferred**: `analyzing-contracts`, `processing-pdfs` (not `contract-analyzer`, `pdf-processor`)
- **Avoid vague names**: `helper`, `utils`, `tools`, `misc`
- **Avoid reserved words**: `anthropic`, `claude`
### Path Handling
- Use `{baseDir}` for paths, **never hardcode** absolute paths
- Use forward slashes (`/`) even on Windows
### Python Scripts
When skills include Python scripts with dependencies:
1. **Use PEP 723 inline metadata** - Declare dependencies in the script header:
```python
# /// script
# requires-python = ">=3.11"
# dependencies = ["requests>=2.28", "pydantic>=2.0"]
# ///
```
2. **Use `uv run`** - Enables automatic dependency resolution:
```bash
uv run {baseDir}/scripts/process.py input.pdf
```
3. **Include `pyproject.toml`** - Keep in `scripts/` for development tooling (ruff, etc.)
4. **Document system dependencies** - List non-Python deps (poppler, tesseract) in workflows with platform-specific install commands
### Hooks
PreToolUse hooks run on every Bash command—performance is critical:
- **Prefer shell + jq** over Python—interpreter startup (Python + tree-sitter) adds noticeable latency
- **Fast-fail early** - exit 0 immediately for non-matching commands so most invocations are instant
- **Favor regex over AST parsing** - accept rare false positives if performance gain is significant and Claude can rephrase
- **Anticipate false positive patterns** - diagnostic commands (`which python`), search tools (`grep python`), and filenames (`cat python.txt`) shouldn't trigger interception
- **Document tradeoffs** in PR descriptions so reviewers understand deliberate design choices
## Quality Standards
These are house standards on top of Anthropic's requirements.
### Description Quality
Your skill competes with 100+ others. The description must trigger correctly.
- **Third-person voice**: "Analyzes X" not "I help with X"
- **Include triggers**: "Use when auditing Solidity" not just "Smart contract tool"
- **Be specific**: "Detects reentrancy vulnerabilities" not "Helps with security"
### Value-Add
Skills should provide guidance Claude doesn't already have, not duplicate reference material.
- **Behavioral guidance over reference dumps** - Don't paste entire specs; teach when and how to look things up
- **Explain WHY, not just WHAT** - Include trade-offs, decision criteria, judgment calls
- **Document anti-patterns WITH explanations** - Say why something is wrong, not just that it's wrong
### Scope Boundaries
Prescriptiveness should match task risk:
- **Strict for fragile tasks** - Security audits, crypto implementations, compliance checks need rigid step-by-step enforcement
- **Flexible for variable tasks** - Code exploration, documentation, refactoring can offer options and judgment calls
### Required Sections
Every SKILL.md must include:
```markdown
## When to Use
[Specific scenarios where this skill applies]
## When NOT to Use
[Scenarios where another approach is better]
```
### Security Skills
For audit/security skills, also include:
```markdown
## Rationalizations to Reject
[Common shortcuts or rationalizations that lead to missed findings]
```
### Content Organization
- Keep SKILL.md **under 500 lines** - split into `references/`, `workflows/`
- Use **progressive disclosure** - quick start first, details in linked files
- **One level deep** - SKILL.md links to files, files don't chain to more files
Note: Directory depth is fine (`references/guides/topic.md`). Reference *chains* are not (`SKILL.md → file1.md → file2.md` where file1 references file2). The problem is chained references, not nested folders.
### Progressive Disclosure Pattern
```markdown
## Quick Start
[Core instructions here]
## Advanced Usage
See [ADVANCED.md](references/ADVANCED.md) for detailed patterns.
## API Reference
See [API.md](references/API.md) for complete method documentation.
```
## Curation Policy
This is a **curated** marketplace. Submissions are reviewed for quality and safety before merging.
### What We Look For
- **Safe hooks and scripts** - reviewers read every line of shell/Python in hooks and scripts; no network calls without documented justification
- **Genuine value** - the skill teaches Claude something it doesn't already know
- **Quality bar** - meets the standards above (frontmatter, sections, descriptions)
- **Originality** - not a trivial wrapper or duplicate of an existing skill
### What Gets Rejected
- Hooks or scripts that make network requests without clear, documented purpose
- Hooks that intercept tool calls to inject unrelated behavior
- Obfuscated code (base64, eval, encoded strings)
- Skills that are purely self-promotional with no real content
- Duplicate submissions of existing skills
### Review Process
- At least one CODEOWNER approval required
- Hooks and scripts get line-by-line review — reviewers should run them locally
- Version bumps to existing plugins get the same scrutiny as new submissions
## PR Checklist
Before submitting:
**Technical (CI validates these):**
- [ ] Valid YAML frontmatter with `name` and `description`
- [ ] Name is kebab-case, ≤64 characters
- [ ] All referenced files exist
- [ ] No hardcoded paths (`/Users/...`, `/home/...`)
**Quality (reviewers check these):**
- [ ] Description triggers correctly (third-person, specific)
- [ ] "When to use" and "When NOT to use" sections present
- [ ] Examples are concrete (input → output)
- [ ] Explains WHY, not just WHAT
**Documentation:**
- [ ] Plugin has README.md
- [ ] Added to root README.md table
- [ ] Registered in marketplace.json
**Version updates (for existing plugins):**
- [ ] Increment version in both `plugin.json` and `.claude-plugin/marketplace.json` when making substantive changes (clients only update plugins when the version number increases)
- [ ] Ensure version numbers match between `plugin.json` and `.claude-plugin/marketplace.json`
CODEOWNERS
+5
View File
@@ -0,0 +1,5 @@
# Default owner for everything
* @dguido
# Plugin-specific owners (alphabetical)
/plugins/ask-questions-if-underspecified/ @kevin-valerio @dguido
LICENSE
+427
View File
@@ -0,0 +1,427 @@
Attribution-ShareAlike 4.0 International
=======================================================================
Creative Commons Corporation ("Creative Commons") is not a law firm and
does not provide legal services or legal advice. Distribution of
Creative Commons public licenses does not create a lawyer-client or
other relationship. Creative Commons makes its licenses and related
information available on an "as-is" basis. Creative Commons gives no
warranties regarding its licenses, any material licensed under their
terms and conditions, or any related information. Creative Commons
disclaims all liability for damages resulting from their use to the
fullest extent possible.
Using Creative Commons Public Licenses
Creative Commons public licenses provide a standard set of terms and
conditions that creators and other rights holders may use to share
original works of authorship and other material subject to copyright
and certain other rights specified in the public license below. The
following considerations are for informational purposes only, are not
exhaustive, and do not form part of our licenses.
Considerations for licensors: Our public licenses are
intended for use by those authorized to give the public
permission to use material in ways otherwise restricted by
copyright and certain other rights. Our licenses are
irrevocable. Licensors should read and understand the terms
and conditions of the license they choose before applying it.
Licensors should also secure all rights necessary before
applying our licenses so that the public can reuse the
material as expected. Licensors should clearly mark any
material not subject to the license. This includes other CC-
licensed material, or material used under an exception or
limitation to copyright. More considerations for licensors:
wiki.creativecommons.org/Considerations_for_licensors
Considerations for the public: By using one of our public
licenses, a licensor grants the public permission to use the
licensed material under specified terms and conditions. If
the licensor's permission is not necessary for any reason--for
example, because of any applicable exception or limitation to
copyright--then that use is not regulated by the license. Our
licenses grant only permissions under copyright and certain
other rights that a licensor has authority to grant. Use of
the licensed material may still be restricted for other
reasons, including because others have copyright or other
rights in the material. A licensor may make special requests,
such as asking that all changes be marked or described.
Although not required by our licenses, you are encouraged to
respect those requests where reasonable. More_considerations
for the public:
wiki.creativecommons.org/Considerations_for_licensees
=======================================================================
Creative Commons Attribution-ShareAlike 4.0 International Public
License
By exercising the Licensed Rights (defined below), You accept and agree
to be bound by the terms and conditions of this Creative Commons
Attribution-ShareAlike 4.0 International Public License ("Public
License"). To the extent this Public License may be interpreted as a
contract, You are granted the Licensed Rights in consideration of Your
acceptance of these terms and conditions, and the Licensor grants You
such rights in consideration of benefits the Licensor receives from
making the Licensed Material available under these terms and
conditions.
Section 1 -- Definitions.
a. Adapted Material means material subject to Copyright and Similar
Rights that is derived from or based upon the Licensed Material
and in which the Licensed Material is translated, altered,
arranged, transformed, or otherwise modified in a manner requiring
permission under the Copyright and Similar Rights held by the
Licensor. For purposes of this Public License, where the Licensed
Material is a musical work, performance, or sound recording,
Adapted Material is always produced where the Licensed Material is
synched in timed relation with a moving image.
b. Adapter's License means the license You apply to Your Copyright
and Similar Rights in Your contributions to Adapted Material in
accordance with the terms and conditions of this Public License.
c. BY-SA Compatible License means a license listed at
creativecommons.org/compatiblelicenses, approved by Creative
Commons as essentially the equivalent of this Public License.
d. Copyright and Similar Rights means copyright and/or similar rights
closely related to copyright including, without limitation,
performance, broadcast, sound recording, and Sui Generis Database
Rights, without regard to how the rights are labeled or
categorized. For purposes of this Public License, the rights
specified in Section 2(b)(1)-(2) are not Copyright and Similar
Rights.
e. Effective Technological Measures means those measures that, in the
absence of proper authority, may not be circumvented under laws
fulfilling obligations under Article 11 of the WIPO Copyright
Treaty adopted on December 20, 1996, and/or similar international
agreements.
f. Exceptions and Limitations means fair use, fair dealing, and/or
any other exception or limitation to Copyright and Similar Rights
that applies to Your use of the Licensed Material.
g. License Elements means the license attributes listed in the name
of a Creative Commons Public License. The License Elements of this
Public License are Attribution and ShareAlike.
h. Licensed Material means the artistic or literary work, database,
or other material to which the Licensor applied this Public
License.
i. Licensed Rights means the rights granted to You subject to the
terms and conditions of this Public License, which are limited to
all Copyright and Similar Rights that apply to Your use of the
Licensed Material and that the Licensor has authority to license.
j. Licensor means the individual(s) or entity(ies) granting rights
under this Public License.
k. Share means to provide material to the public by any means or
process that requires permission under the Licensed Rights, such
as reproduction, public display, public performance, distribution,
dissemination, communication, or importation, and to make material
available to the public including in ways that members of the
public may access the material from a place and at a time
individually chosen by them.
l. Sui Generis Database Rights means rights other than copyright
resulting from Directive 96/9/EC of the European Parliament and of
the Council of 11 March 1996 on the legal protection of databases,
as amended and/or succeeded, as well as other essentially
equivalent rights anywhere in the world.
m. You means the individual or entity exercising the Licensed Rights
under this Public License. Your has a corresponding meaning.
Section 2 -- Scope.
a. License grant.
1. Subject to the terms and conditions of this Public License,
the Licensor hereby grants You a worldwide, royalty-free,
non-sublicensable, non-exclusive, irrevocable license to
exercise the Licensed Rights in the Licensed Material to:
a. reproduce and Share the Licensed Material, in whole or
in part; and
b. produce, reproduce, and Share Adapted Material.
2. Exceptions and Limitations. For the avoidance of doubt, where
Exceptions and Limitations apply to Your use, this Public
License does not apply, and You do not need to comply with
its terms and conditions.
3. Term. The term of this Public License is specified in Section
6(a).
4. Media and formats; technical modifications allowed. The
Licensor authorizes You to exercise the Licensed Rights in
all media and formats whether now known or hereafter created,
and to make technical modifications necessary to do so. The
Licensor waives and/or agrees not to assert any right or
authority to forbid You from making technical modifications
necessary to exercise the Licensed Rights, including
technical modifications necessary to circumvent Effective
Technological Measures. For purposes of this Public License,
simply making modifications authorized by this Section 2(a)
(4) never produces Adapted Material.
5. Downstream recipients.
a. Offer from the Licensor -- Licensed Material. Every
recipient of the Licensed Material automatically
receives an offer from the Licensor to exercise the
Licensed Rights under the terms and conditions of this
Public License.
b. Additional offer from the Licensor -- Adapted Material.
Every recipient of Adapted Material from You
automatically receives an offer from the Licensor to
exercise the Licensed Rights in the Adapted Material
under the conditions of the Adapter's License You apply.
c. No downstream restrictions. You may not offer or impose
any additional or different terms or conditions on, or
apply any Effective Technological Measures to, the
Licensed Material if doing so restricts exercise of the
Licensed Rights by any recipient of the Licensed
Material.
6. No endorsement. Nothing in this Public License constitutes or
may be construed as permission to assert or imply that You
are, or that Your use of the Licensed Material is, connected
with, or sponsored, endorsed, or granted official status by,
the Licensor or others designated to receive attribution as
provided in Section 3(a)(1)(A)(i).
b. Other rights.
1. Moral rights, such as the right of integrity, are not
licensed under this Public License, nor are publicity,
privacy, and/or other similar personality rights; however, to
the extent possible, the Licensor waives and/or agrees not to
assert any such rights held by the Licensor to the limited
extent necessary to allow You to exercise the Licensed
Rights, but not otherwise.
2. Patent and trademark rights are not licensed under this
Public License.
3. To the extent possible, the Licensor waives any right to
collect royalties from You for the exercise of the Licensed
Rights, whether directly or through a collecting society
under any voluntary or waivable statutory or compulsory
licensing scheme. In all other cases the Licensor expressly
reserves any right to collect such royalties.
Section 3 -- License Conditions.
Your exercise of the Licensed Rights is expressly made subject to the
following conditions.
a. Attribution.
1. If You Share the Licensed Material (including in modified
form), You must:
a. retain the following if it is supplied by the Licensor
with the Licensed Material:
i. identification of the creator(s) of the Licensed
Material and any others designated to receive
attribution, in any reasonable manner requested by
the Licensor (including by pseudonym if
designated);
ii. a copyright notice;
iii. a notice that refers to this Public License;
iv. a notice that refers to the disclaimer of
warranties;
v. a URI or hyperlink to the Licensed Material to the
extent reasonably practicable;
b. indicate if You modified the Licensed Material and
retain an indication of any previous modifications; and
c. indicate the Licensed Material is licensed under this
Public License, and include the text of, or the URI or
hyperlink to, this Public License.
2. You may satisfy the conditions in Section 3(a)(1) in any
reasonable manner based on the medium, means, and context in
which You Share the Licensed Material. For example, it may be
reasonable to satisfy the conditions by providing a URI or
hyperlink to a resource that includes the required
information.
3. If requested by the Licensor, You must remove any of the
information required by Section 3(a)(1)(A) to the extent
reasonably practicable.
b. ShareAlike.
In addition to the conditions in Section 3(a), if You Share
Adapted Material You produce, the following conditions also apply.
1. The Adapter's License You apply must be a Creative Commons
license with the same License Elements, this version or
later, or a BY-SA Compatible License.
2. You must include the text of, or the URI or hyperlink to, the
Adapter's License You apply. You may satisfy this condition
in any reasonable manner based on the medium, means, and
context in which You Share Adapted Material.
3. You may not offer or impose any additional or different terms
or conditions on, or apply any Effective Technological
Measures to, Adapted Material that restrict exercise of the
rights granted under the Adapter's License You apply.
Section 4 -- Sui Generis Database Rights.
Where the Licensed Rights include Sui Generis Database Rights that
apply to Your use of the Licensed Material:
a. for the avoidance of doubt, Section 2(a)(1) grants You the right
to extract, reuse, reproduce, and Share all or a substantial
portion of the contents of the database;
b. if You include all or a substantial portion of the database
contents in a database in which You have Sui Generis Database
Rights, then the database in which You have Sui Generis Database
Rights (but not its individual contents) is Adapted Material,
including for purposes of Section 3(b); and
c. You must comply with the conditions in Section 3(a) if You Share
all or a substantial portion of the contents of the database.
For the avoidance of doubt, this Section 4 supplements and does not
replace Your obligations under this Public License where the Licensed
Rights include other Copyright and Similar Rights.
Section 5 -- Disclaimer of Warranties and Limitation of Liability.
a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
c. The disclaimer of warranties and limitation of liability provided
above shall be interpreted in a manner that, to the extent
possible, most closely approximates an absolute disclaimer and
waiver of all liability.
Section 6 -- Term and Termination.
a. This Public License applies for the term of the Copyright and
Similar Rights licensed here. However, if You fail to comply with
this Public License, then Your rights under this Public License
terminate automatically.
b. Where Your right to use the Licensed Material has terminated under
Section 6(a), it reinstates:
1. automatically as of the date the violation is cured, provided
it is cured within 30 days of Your discovery of the
violation; or
2. upon express reinstatement by the Licensor.
For the avoidance of doubt, this Section 6(b) does not affect any
right the Licensor may have to seek remedies for Your violations
of this Public License.
c. For the avoidance of doubt, the Licensor may also offer the
Licensed Material under separate terms or conditions or stop
distributing the Licensed Material at any time; however, doing so
will not terminate this Public License.
d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
License.
Section 7 -- Other Terms and Conditions.
a. The Licensor shall not be bound by any additional or different
terms or conditions communicated by You unless expressly agreed.
b. Any arrangements, understandings, or agreements regarding the
Licensed Material not stated herein are separate from and
independent of the terms and conditions of this Public License.
Section 8 -- Interpretation.
a. For the avoidance of doubt, this Public License does not, and
shall not be interpreted to, reduce, limit, restrict, or impose
conditions on any use of the Licensed Material that could lawfully
be made without permission under this Public License.
b. To the extent possible, if any provision of this Public License is
deemed unenforceable, it shall be automatically reformed to the
minimum extent necessary to make it enforceable. If the provision
cannot be reformed, it shall be severed from this Public License
without affecting the enforceability of the remaining terms and
conditions.
c. No term or condition of this Public License will be waived and no
failure to comply consented to unless expressly agreed to by the
Licensor.
d. Nothing in this Public License constitutes or may be interpreted
as a limitation upon, or waiver of, any privileges and immunities
that apply to the Licensor or You, including from the legal
processes of any jurisdiction or authority.
=======================================================================
Creative Commons is not a party to its public
licenses. Notwithstanding, Creative Commons may elect to apply one of
its public licenses to material it publishes and in those instances
will be considered the "Licensor." The text of the Creative Commons
public licenses is dedicated to the public domain under the CC0 Public
Domain Dedication. Except for the limited purpose of indicating that
material is shared under a Creative Commons public license or as
otherwise permitted by the Creative Commons policies published at
creativecommons.org/policies, Creative Commons does not authorize the
use of the trademark "Creative Commons" or any other trademark or logo
of Creative Commons without its prior written consent including,
without limitation, in connection with any unauthorized modifications
to any of its public licenses or any other arrangements,
understandings, or agreements concerning use of licensed material. For
the avoidance of doubt, this paragraph does not form part of the
public licenses.
Creative Commons may be contacted at creativecommons.org.
README.md
+63
View File
@@ -0,0 +1,63 @@
# Curated Skills Marketplace
A curated, community-vetted Claude Code plugin marketplace. Every skill here has been reviewed for quality and safety before inclusion.
## Why Curated?
The Claude Code skills ecosystem is growing fast, but not everything out there is trustworthy. Some published skills have been found to contain backdoors or malicious hooks. This repo exists as a **gate**—a place where the community can submit skills they use and trust, with review and CI checks enforcing quality and safety standards.
If you're using a skill from the wild, consider submitting it here so others can benefit from reviewed, vetted versions.
## Installation
### Add the Marketplace
```
/plugin marketplace add trailofbits/skills-curated
```
### Browse and Install Plugins
```
/plugin menu
```
### Local Development
To add the marketplace locally (e.g., for testing or development), navigate to the **parent directory** of this repository:
```
cd /path/to/parent # e.g., if repo is at ~/projects/skills-curated, be in ~/projects
/plugins marketplace add ./skills-curated
```
## Available Plugins
### Development
| Plugin | Description |
|--------|-------------|
| [ask-questions-if-underspecified](plugins/ask-questions-if-underspecified/) | Clarify requirements before implementing |
## Trophy Case
Bugs discovered using curated skills. Found something? [Let us know!](https://github.com/trailofbits/skills-curated/issues/new?template=trophy-case.yml)
When reporting bugs you've found, feel free to mention:
> Found using [Curated Skills](https://github.com/trailofbits/skills-curated)
| Skill | Bug |
|-------|-----|
## Contributing
We welcome contributions! Please see [CLAUDE.md](CLAUDE.md) for skill authoring guidelines.
Every submission goes through code review. We check for:
- Malicious hooks, scripts, or commands
- Quality and completeness (frontmatter, required sections, examples)
- Genuine value-add over Claude's built-in capabilities
## License
This work is licensed under a [Creative Commons Attribution-ShareAlike 4.0 International License](https://creativecommons.org/licenses/by-sa/4.0/).
plugins/ask-questions-if-underspecified/.claude-plugin/plugin.json
+10
View File
@@ -0,0 +1,10 @@
{
"name": "ask-questions-if-underspecified",
"version": "1.0.1",
"description": "Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.",
"author": {
"name": "Kevin Valerio",
"email": "opensource@trailofbits.com",
"url": "https://github.com/trailofbits"
}
}
plugins/ask-questions-if-underspecified/README.md
+24
View File
@@ -0,0 +1,24 @@
# Ask Questions If Underspecified
Ask the minimum set of clarifying questions needed to avoid wrong work.
**Author:** Kevin Valerio
## When to Use
Use this skill when:
- The request has multiple plausible interpretations
- Success criteria, scope, constraints, or environment details are unclear
- Starting implementation without clarification risks doing the wrong work
## What It Does
- Asks 1-5 must-have questions in a scannable, answerable format (multiple choice + defaults)
- Pauses before acting until required answers are provided (unless the user approves proceeding on stated assumptions)
- Restates confirmed requirements before starting work
## Installation
```
/plugin install trailofbits/skills-curated/plugins/ask-questions-if-underspecified
```
plugins/ask-questions-if-underspecified/skills/ask-questions-if-underspecified/SKILL.md
+85
View File
@@ -0,0 +1,85 @@
---
name: ask-questions-if-underspecified
description: Clarify requirements before implementing. Use when serious doubts arise.
---
# Ask Questions If Underspecified
## When to Use
Use this skill when a request has multiple plausible interpretations or key details (objective, scope, constraints, environment, or safety) are unclear.
## When NOT to Use
Do not use this skill when the request is already clear, or when a quick, low-risk discovery read can answer the missing details.
## Goal
Ask the minimum set of clarifying questions needed to avoid wrong work; do not start implementing until the must-have questions are answered (or the user explicitly approves proceeding with stated assumptions).
## Workflow
### 1) Decide whether the request is underspecified
Treat a request as underspecified if after exploring how to perform the work, some or all of the following are not clear:
- Define the objective (what should change vs stay the same)
- Define "done" (acceptance criteria, examples, edge cases)
- Define scope (which files/components/users are in/out)
- Define constraints (compatibility, performance, style, deps, time)
- Identify environment (language/runtime versions, OS, build/test runner)
- Clarify safety/reversibility (data migration, rollout/rollback, risk)
If multiple plausible interpretations exist, assume it is underspecified.
### 2) Ask must-have questions first (keep it small)
Ask 1-5 questions in the first pass. Prefer questions that eliminate whole branches of work.
Make questions easy to answer:
- Optimize for scannability (short, numbered questions; avoid paragraphs)
- Offer multiple-choice options when possible
- Suggest reasonable defaults when appropriate (mark them clearly as the default/recommended choice; bold the recommended choice in the list, or if you present options in a code block, put a bold "Recommended" line immediately above the block and also tag defaults inside the block)
- Include a fast-path response (e.g., reply `defaults` to accept all recommended/default choices)
- Include a low-friction "not sure" option when helpful (e.g., "Not sure - use default")
- Separate "Need to know" from "Nice to know" if that reduces friction
- Structure options so the user can respond with compact decisions (e.g., `1b 2a 3c`); restate the chosen options in plain language to confirm
### 3) Pause before acting
Until must-have answers arrive:
- Do not run commands, edit files, or produce a detailed plan that depends on unknowns
- Do perform a clearly labeled, low-risk discovery step only if it does not commit you to a direction (e.g., inspect repo structure, read relevant config files)
If the user explicitly asks you to proceed without answers:
- State your assumptions as a short numbered list
- Ask for confirmation; proceed only after they confirm or correct them
### 4) Confirm interpretation, then proceed
Once you have answers, restate the requirements in 1-3 sentences (including key constraints and what success looks like), then start work.
## Question templates
- "Before I start, I need: (1) ..., (2) ..., (3) .... If you don't care about (2), I will assume ...."
- "Which of these should it be? A) ... B) ... C) ... (pick one)"
- "What would you consider 'done'? For example: ..."
- "Any constraints I must follow (versions, performance, style, deps)? If none, I will target the existing project defaults."
- Use numbered questions with lettered options and a clear reply format
```text
1) Scope?
a) Minimal change (default)
b) Refactor while touching the area
c) Not sure - use default
2) Compatibility target?
a) Current project defaults (default)
b) Also support older versions: <specify>
c) Not sure - use default
Reply with: defaults (or 1a 2a)
```
## Anti-patterns
- Don't ask questions you can answer with a quick, low-risk discovery read (e.g., configs, existing patterns, docs).
- Don't ask open-ended questions if a tight multiple-choice or yes/no would eliminate ambiguity faster.
pyproject.toml
+16
View File
@@ -0,0 +1,16 @@
[project]
name = "skills-curated"
version = "0.0.0"
description = "Curated Claude Code Skills Marketplace - linting configuration"
requires-python = ">=3.11"
[tool.ruff]
line-length = 100
target-version = "py311"
[tool.ruff.lint]
select = ["E", "F", "I", "UP", "B", "SIM"]
[tool.ruff.lint.per-file-ignores]
"**/tests/**/*.py" = ["F401", "SIM118"]
"**/test_samples/**/*.py" = ["F", "E", "B"]