Supabase Schema From Requirements
jeremylongshore/tons-of-skills-marketplace
Design Supabase Postgres schema from business requirements with migrations, RLS, and types.
Trace how clients, CDNs, proxies, protocol translators, gateways, frameworks, and origins derive HTTP message boundaries, authority, paths, queries, and trusted forwarding metadata.
Install Trace Request Normalization
$ npx skills add cyberful/cyberful --skill trace-request-normalization -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cyberful/cyberful trace-request-normalization --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-request-normalization .claude/skills/trace-request-normalization && 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-request-normalization" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/trace-request-normalization into .claude/skills/trace-request-normalization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-request-normalization", 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-request-normalizationType 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-request-normalization -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cyberful/cyberful trace-request-normalization --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-request-normalization .agents/skills/trace-request-normalization && 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-request-normalization" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/trace-request-normalization into .agents/skills/trace-request-normalization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-request-normalization", 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-request-normalization -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cyberful/cyberful trace-request-normalization --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-request-normalization .cursor/skills/trace-request-normalization && 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-request-normalization" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/trace-request-normalization into .cursor/skills/trace-request-normalization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-request-normalization", 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-request-normalization--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-request-normalization -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cyberful/cyberful trace-request-normalization --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-request-normalization .gemini/skills/trace-request-normalization && 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-request-normalization" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/trace-request-normalization into .gemini/skills/trace-request-normalization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-request-normalization", 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-request-normalizationInstalls 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-request-normalization -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-request-normalization .github/skills/trace-request-normalization && 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-request-normalization" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/trace-request-normalization into .github/skills/trace-request-normalization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-request-normalization", 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-request-normalization -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-request-normalization --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-request-normalization .opencode/skills/trace-request-normalization && 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-request-normalization" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/trace-request-normalization into .opencode/skills/trace-request-normalization/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trace-request-normalization", 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-request-normalization- GitHub stars
- 135
- Token cost
- ~711 tokens
- SKILL.md length
- 239 words
- Files
- 9 (incl. scripts, references, assets)
- Skills in repo
- 85
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Trace how clients, CDNs, proxies, protocol translators, gateways, frameworks, and origins derive HTTP message boundaries, authority, paths, queries, and trusted forwarding metadata.
- Localize request-smuggling
- SKILL.md covers Build the hop ledger, Trace one semantic dimension… and Confirmation standard
- Runs Python scripts from its folder
- Routing-confusion
What it does
Trace Request Normalization is an agent skill from cyberful/cyberful. Trace how clients, CDNs, proxies, protocol translators, gateways, frameworks, and origins derive HTTP message boundaries, authority, paths, queries, and trusted forwarding metadata. Use to localize request-smuggling, routing-confusion, duplicate-field, decoding-order, or intermediary normalization hypotheses before bounded validation.
Its SKILL.md is about 710 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/normalization-campaign.example.json` and `assets/normalization-campaign.schema.json`).
It sits in Databases, covering Database schema design and Translation. 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
- Localize request-smuggling
- Routing-confusion
- Duplicate-field
- Intermediary normalization hypotheses before bounded validation
Example prompts
- “/trace-request-normalization”
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
Trace Request Normalization loads about 711 tokens when it runs, and up to ~1k if it reads all its reference files. Until then it costs about 91 tokens; SKILL.md has 239 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). 239 words, ~711 tokens.
Download SKILL.mdSave it as
.claude/skills/trace-request-normalization/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.- name
- trace-request-normalization
- description
- Trace how clients, CDNs, proxies, protocol translators, gateways, frameworks, and origins derive HTTP message boundaries, authority, paths, queries, and trusted forwarding metadata. Use to localize request-smuggling, routing-confusion, duplicate-field, decoding-order, or intermediary normalization hypotheses before bounded validation.
- metadata.domain
- application-security
- metadata.subdomain
- http-normalization
- metadata.triggers
- http request normalization, request smuggling trace, proxy origin disagreement, duplicate header parsing, path decoding differential, forwarded header trust
- metadata.tags
- http, normalization, reverse-proxy, request-smuggling, routing, parser-differential
Trace Request Normalization
Localize the exact adjacent pair of HTTP components that assigns different semantics to the same authorized request. A response difference without a hop-level interpretation difference is only a lead.
Build the hop ledger
Record client, edge, cache, translator, gateway, mesh, framework, router, and origin in order. For each hop capture protocol version, connection reuse, framing owner, authority source, forwarded-field policy, path and query decoding, duplicate handling, hop-by-hop removal, body limits, and observable logs.
Read references/normalization-ledger.md before constructing a hypothesis. Preserve original bytes and component-local representations; do not normalize the evidence before comparison.
Trace one semantic dimension at a time
Compare paired controls for authority, path, query, method, duplicate fields, transfer framing, content length, encoded delimiters, Unicode, and protocol translation. Predict the two component interpretations before sending any active case.
Use scripts/run_normalization_harness.py only for safe HTTP-level variants after the exact origin, request ceiling, rate, and authorization reference are explicit. The campaign file cannot select transport: non-loopback traffic requires the proxy and CA route inherited from the Cyberful gateway after the model boundary, while literal-IP loopback traffic explicitly disables proxies. The harness does not emit malformed framing or claim request desynchronization; raw-socket or shared-connection work requires a separately approved specialist setup.
Confirmation standard
Report the original request, both interpretations, components and versions, connection and routing prerequisites, a matched control, observable security effect, and affected authority. Do not generalize from a status code, reflection, timeout, or backend error alone.
© 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/trace-request-normalization of cyberful/cyberful.
- SKILL.md
- agents/openai.yaml
- assets/normalization-campaign.example.json
- assets/normalization-campaign.schema.json
- assets/normalization-evidence.schema.json
- references/normalization-ledger.md
- scripts/manifest.json
- scripts/run_normalization_harness.py
- tests/test_run_normalization_harness.py
Open the folder on GitHubat commit ec598a6
Compare with similar skills
Trace Request Normalization 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 Request Normalization this skillcyberful/cyberful | 135 | — | ~711 | Automated safety check: Pass | AGPL-3.0 | |
| Supabase Schema From Requirementsjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Ncats AraxK-Dense-AI/scientific-agent-skills | 48k | 2 repos | ~2.3k | Automated safety check: Notes | MIT | |
| Query Pipelinedotnet/efcore | 15k | — | ~194 | Automated safety check: Pass | MIT | |
| 511 Frameworks Micronaut Jdbcjabrena/plinth | 446 | — | ~872 | Automated safety check: Pass | Apache-2.0 | |
| SQL To Business Logicnimrodfisher/data-analytics-skills | 465 | — | ~636 | Automated safety check: Pass | MIT |
Similar skills
Ncats Arax
K-Dense-AI/scientific-agent-skills
Queries the NCATS Translator ARAX production API for bounded, typed, provenance-rich one-hop and endpoint-pinned two-hop biomedical knowledge-graph relationships.
- Official
Query Pipeline
dotnet/efcore
Implementation details for EF Core LINQ query translation, SQL generation, and bulk operations (ExecuteUpdate/ExecuteDelete).
511 Frameworks Micronaut Jdbc
jabrena/plinth
A skill your agent uses when you need programmatic JDBC in Micronaut — pooled DataSource, parameterized SQL, io.micronaut.transaction.annotation.Transactional, batching, and domain exception…
SQL To Business Logic
nimrodfisher/data-analytics-skills
Translate SQL queries into plain language business logic. An agent skill from nimrodfisher/data-analytics-skills.
Entity Framework Core
managedcode/dotnet-skills
Design, tune, or review EF Core data access with proper modeling, migrations, query translation, performance, and lifetime management for modern .NET applications.
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 Request Normalization
What does Trace Request Normalization do?
Trace how clients, CDNs, proxies, protocol translators, gateways, frameworks, and origins derive HTTP message boundaries, authority, paths, queries, and trusted forwarding metadata. Trace Request Normalization is an agent skill from cyberful/cyberful. Trace how clients, CDNs, proxies, protocol translators, gateways, frameworks, and origins derive HTTP message boundaries, authority, paths, queries, and trusted forwarding metadata.
When should I use Trace Request Normalization?
Trace Request Normalization fits situations like: localize request-smuggling; routing-confusion; duplicate-field; intermediary normalization hypotheses before bounded validation.
How do I install Trace Request Normalization in Claude Code?
Run `npx skills add cyberful/cyberful --skill trace-request-normalization -a claude-code`. Or copy the skill folder (cyberful/builtin/skills/trace-request-normalization in cyberful/cyberful) into .claude/skills/trace-request-normalization in your project. Claude Code loads it when a task matches its description.
How do I install Trace Request Normalization in Codex?
Run `npx skills add cyberful/cyberful --skill trace-request-normalization -a codex`. Or copy the skill folder (cyberful/builtin/skills/trace-request-normalization in cyberful/cyberful) into .agents/skills/trace-request-normalization in your project. Codex loads it when a task matches its description.
Can I use Trace Request Normalization 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-request-normalization -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-request-normalization, .gemini/skills/trace-request-normalization, .github/skills/trace-request-normalization and .opencode/skills/trace-request-normalization in your project.
What does Trace Request Normalization need to run?
Going by SKILL.md and its folder, Trace Request Normalization needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Trace Request Normalization 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 Request Normalization 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 Trace Request Normalization use?
Trace Request Normalization 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 Request Normalization use?
About 711 tokens (SKILL.md is roughly 2.8k 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 308 tokens, read only when the agent opens those files.
What are the alternatives to Trace Request Normalization?
Skills that share tags, products or a category with Trace Request Normalization: Supabase Schema From Requirements (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Ncats Arax (K-Dense-AI/scientific-agent-skills, 48k stars), Query Pipeline (dotnet/efcore, 15k stars) and 511 Frameworks Micronaut Jdbc (jabrena/plinth, 446 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Trace Request Normalization?
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.