CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

api-grpc

gRPC API exploitation — reflection-based discovery via grpcurl, protobuf fuzzing, missing authz on streaming RPCs, gRPC-Web → backend SSRF, mTLS bypass, metadata header injection, h2c smuggling against gRPC fronts.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/exploit/api/grpc/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, executable cheat-sheet that respects token budget and assumes competence — nearly every line is a runnable command. Its main weaknesses are the absence of validation/feedback steps in the discovery and fuzzing workflows and a few commands that depend on unexplained external tools.

Suggestions

Add validation checkpoints to the workflows, e.g. check the reflection listing succeeded before fuzzing, and capture/triage errors per method in the enumeration loop instead of blindly piping to head -5.

Note how to obtain the external tools invoked (h2csmuggler.py, grpcfuzzer/Mayhem) with a repo URL or install line, so the commands are fully executable.

Turn the 'References' section into concrete, resolvable pointers (URLs for the NCC Group whitepaper and grpcurl manual) rather than unlabeled titles.

DimensionReasoningScore

Conciseness

The body is lean throughout: each section is a command block with a one-line setup ('Many implementations enforce auth on unary RPCs but skip server-streaming'), with zero padding or explanation of gRPC concepts Claude already knows.

5 / 5

Actionability

Most guidance is copy-paste-ready grpcurl/curl commands, but a few have minor gaps: external tools (h2csmuggler.py, Mayhem/grpcfuzzer) are invoked without acquisition instructions, and several examples are speculative patterns ('If the Envoy filter is misconfigured') rather than verified commands.

4 / 5

Workflow Clarity

A rough discover → attack → fuzz sequence exists, but there are no validation checkpoints anywhere; the fuzz loop batch-invokes every reflected method against a live target with no verification or error-handling step, which caps workflow clarity at 3 per the rubric's batch-operation rule.

3 / 5

Progressive Disclosure

Well-organized sections with no bundle files to navigate, and the ~100-line body stays appropriately at overview depth; however the trailing 'References' are vague external citations ('DEFCON 30 "Cloud Native Track"') rather than clearly signaled, resolvable pointers.

4 / 5

Total

16

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-differentiated description that concretely enumerates its capabilities, but it entirely lacks a 'when to use' trigger clause, leaving completeness at the rubric's cap. Adding a 'Use when...' sentence covering gRPC, protobuf, .proto, and HTTP/2 contexts would lift it to the top tier.

Suggestions

Append an explicit trigger clause, e.g. 'Use when testing gRPC or gRPC-Web endpoints, .proto files, or HTTP/2 APIs' — its absence currently caps completeness at 3.

Work natural synonyms into the description (protocol buffers, .proto, HTTP/2) so the description matches the fuller keyword set already present in metadata.when_to_use.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — 'reflection-based discovery via grpcurl, protobuf fuzzing, missing authz on streaming RPCs, gRPC-Web → backend SSRF, mTLS bypass, metadata header injection, h2c smuggling' — giving comprehensive, specific coverage of the gRPC attack domain rather than vague claims.

5 / 5

Completeness

The 'what' is clearly and concretely answered (enumerated attack techniques), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Strong natural keywords a user would say (gRPC, grpcurl, protobuf, streaming, mTLS, h2c, gRPC-Web), but common variations like 'protocol buffers', 'HTTP/2', or '.proto' files are absent from the description itself.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (gRPC-specific exploitation) with distinct triggers (grpcurl, protobuf, h2c, mTLS, gRPC-Web) that would not naturally fire for a generic API or web pentest skill.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/exploit/api/grpc/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.