Habilidades basin
📦
basin
Revisión del contenido r1 Riesgo alto 🌐 Acceso a red📁 Acceso al sistema de archivos⚙️ Comandos externos
Build Cloudflare Basin Analytics Workflows
Streaming analytics requires coordinated ingestion, table management, and query configuration. This skill provides Cloudflare Basin references and implementation patterns across Pipelines, Catalog, and SQL.
Compatible con: Claude Codex Code(CC)
Detente y solicita confirmación antes de instalar.
Revisa el plan y obtén el consentimiento explícito del usuario antes de modificar archivos.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
Solicitud de agente
Review the Skillstore skill "basin" from https://skillstore.io/skills/cloudflare-basin.md and its manifest at https://skillstore.io/api/skills/cloudflare-basin/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "basin". Which services should receive Worker events and support SQL reports?
Resultado esperado:
- Use a Basin Pipelines stream to receive validated Worker events.
- Connect the stream through row-level transformations to a Basin Catalog Iceberg sink in R2.
- Use Basin SQL for aggregate reports, with scoped credentials and protected dashboard access.
- Verify current command syntax and confirm data delivery after the first flush.
Usando "basin". The stream accepts events, but the table remains empty. What should I check?
Resultado esperado:
- Check pipeline state and failure reason without changing resources.
- Compare events with the stream schema and inspect validation error metrics.
- Check sink credentials, bucket availability, and catalog enablement.
- Allow for the documented first-flush delay and verify both written files and query results.
Usando "basin". Review the dashboard and Logpush examples before production deployment.
Resultado esperado:
- Require caller authentication and authorization before executing dashboard queries.
- Enable ingestion authentication and control request volume.
- Remove raw ClientIP from stored projections; hashing an additional column does not redact the original.
- Check credential presence without printing tokens and store Worker tokens as secrets.
Auditoría de seguridad
Riesgo altov1 • 9/10/2026 Abrir el informe versionado
All 70 static matches are false positives involving documentation links, placeholder URLs, legitimate service requests, SQL identifiers, and TypeScript strings. Four semantic risks concern unauthenticated ingestion, an unprotected analytics endpoint, ineffective IP redaction, and a command that prints an API token. No evidence found of prompt injection, malicious exfiltration, or covert code execution in the reviewed files.
16
Archivos escaneados
1,104
Líneas analizadas
0
Elementos de revisión
0
Falsos positivos ignorados
Preocupaciones de seguridad confirmadas (4)
Alto
Dashboard Worker Exposes Analytics Without Caller Authorization
The Worker matches "/api/analytics", queries with its server-side token, and returns result.rows without checking caller identity or permissions. A public deployment without external protection could disclose analytics and permit repeated billable queries.
The complete handler performs only a pathname check before returning authenticated query results. No caller authentication is shown; external deployment controls could reduce exposure.
Medio
HTTP Ingestion Templates Disable Authentication
The REST example sets "authentication": false, and Terraform also sets authentication = false for HTTP ingestion. If deployed, unauthenticated senders could inject events, corrupt analytics, and increase storage or processing costs.
Both executable configuration examples explicitly disable authentication without requiring an upstream access boundary. Exploitation depends on deploying these examples and accessing the ingest endpoint.
Medio
Claimed IP Redaction Retains Raw Client Addresses
The Logpush transform selects ClientIP alongside sha256(ClientIP) AS hashed_ip while claiming "redact PII at ingest". The stored output retains the original address, so following this example does not achieve the stated redaction.
The same SELECT explicitly includes both the raw ClientIP column and its hash. The misleading redaction comment directly contradicts the output projection.
Medio
Troubleshooting Command Prints Authentication Secret
The checklist recommends "echo $WRANGLER_BASIN_SQL_AUTH_TOKEN" to test token presence. This reveals the complete credential in terminal output and can expose it through captured logs or assistant transcripts.
The command explicitly expands and prints the authentication token rather than checking whether it exists. Further disclosure depends on how terminal output is recorded.
Factores de riesgo
🌐 Acceso a red (26)
references/catalog/api.md:22 references/pipelines/api.md:14 references/pipelines/api.md:29 references/pipelines/api.md:36 references/pipelines/api.md:41 references/pipelines/api.md:109 references/pipelines/api.md:114 references/pipelines/patterns.md:9 references/pipelines/patterns.md:48 references/pipelines/patterns.md:48 references/pipelines/patterns.md:93 references/pipelines/README.md:51 references/sql/api.md:8 references/sql/configuration.md:36 references/sql/patterns.md:52 references/sql/patterns.md:62 references/sql/patterns.md:26 references/sql/patterns.md:22 references/sql/patterns.md:38 references/sql/patterns.md:51 SKILL.md:8 SKILL.md:12 SKILL.md:18 SKILL.md:19 SKILL.md:20 SKILL.md:22
📁 Acceso al sistema de archivos (19)
references/catalog/api.md:30 references/catalog/patterns.md:10 references/catalog/patterns.md:11 references/catalog/README.md:16 references/pipelines/api.md:124 references/pipelines/gotchas.md:45 references/pipelines/patterns.md:122 references/pipelines/patterns.md:125 references/pipelines/patterns.md:130 references/pipelines/README.md:88 references/pipelines/README.md:89 references/sql/api.md:3 references/sql/api.md:96 references/sql/configuration.md:7 references/sql/patterns.md:109 references/sql/patterns.md:114 references/sql/patterns.md:118 references/sql/README.md:63 references/sql/README.md:64
Auditado por: codex
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/cloudflare-basin/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/cloudflare-basin?utm_source=security_passport_badge)Insignia HTML
<a href="https://skillstore.io/skills/cloudflare-basin?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cloudflare-basin/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Tarjeta para insertar
<iframe src="https://skillstore.io/embed/skills/cloudflare-basin.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citas académicas (APA · BibTeX · CFF)
Cita APA
cloudflare. (2026). basin security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cloudflare-basin/audits/1Cita BibTeX
@techreport{cloudflare-cloudflare-basin-2026,
author = {cloudflare},
title = {basin security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cloudflare-basin/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "basin security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "cloudflare"
date-released: "2026-10-09"
url: "https://skillstore.io/skills/cloudflare-basin/audits/1"
identifiers:
- type: other
value: "skillstore:cloudflare-basin:audit:1"
description: "Skillstore immutable audit report identifier"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: Medio 36
Arquitectura
85
Mantenibilidad
87
Contenido
65
Comunidad
83
Cumplimiento de la especificación
Lo que puedes crear
Design a Streaming Analytics Pipeline
Plan event schemas, Worker ingestion, SQL transformations, and Iceberg sinks for an R2 analytics workflow.
Develop a Protected Analytics Dashboard
Adapt the Basin SQL Worker pattern with application access controls, bounded queries, and server-side credential storage.
Diagnose Missing Analytics Events
Investigate pipeline status, delayed flushes, validation errors, sink credentials, and delivery metrics before changing infrastructure.
Prueba estos prompts
Choose the Basin Components
Explain which Basin components fit my event analytics workload: [workload]. Identify required resources and questions before proposing commands.
Plan Authenticated Event Ingestion
Plan a Basin pipeline for [event schema] in [bucket]. Include authenticated ingestion, client validation, scoped credentials, and current Wrangler command checks.
Investigate Missing Events
Events are accepted but missing from [table]. Use these sanitized metrics: [metrics]. Propose read-only checks without printing secrets or deleting resources.
Review an Analytics Architecture
Review [architecture] for Basin analytics. Assess caller authorization, IP minimization, partition filtering, compaction, schema migration, and rollback using current provider references.
Mejores prácticas
- Check current provider documentation and installed tool versions before applying migration commands or permission changes.
- Require ingestion authentication and dashboard authorization; scope credentials and never print secret values during diagnostics.
- Validate events before sending, verify stored output, and use partition filters, query limits, and appropriate table maintenance.
Evitar
- Deploying unauthenticated ingest or dashboard examples directly into production.
- Assuming accepted events are persisted without checking validation errors, sink files, and query results.
- Claiming IP redaction while storing raw addresses, or exposing authentication tokens in troubleshooting output.
Preguntas frecuentes
What does this skill provide?
It provides reference guidance and implementation patterns for Basin Pipelines, Basin Catalog, and Basin SQL over R2.
Does installation create Cloudflare resources?
The reviewed package contains Markdown references, not provisioning scripts. Resource creation requires separately running authorized tools or API requests.
Does it cover the former Cloudflare product names?
Yes. It maps Pipelines, R2 Data Catalog, and R2 SQL to Basin names and warns that command migration requires verification.
Can Basin SQL modify data or replace a transactional database?
No. The references describe Basin SQL as read-only analytics; writes require other engines, and transactional workloads need a suitable database.
Why can accepted events be missing from queries?
Deferred schema validation, first-flush delay, roll intervals, and sink failures can prevent immediate visibility. Check service metrics and stored files.
Are the examples ready for production?
No. Review access controls, ingestion authentication, IP handling, secret diagnostics, current API behavior, and credential scope before deployment.
Detalles del desarrollador
Autor
cloudflareLicencia
MIT
Revisión de Skillstore
r1
Aviso de versión
El autor no declaró una versión.
Repositorio
https://github.com/cloudflare/skills/tree/a18ffe2a99448ebff262fc87915b0fd14bab9b70/skills/basinRef.
e406bf64b5db6e514879399e87b346fa7ff7c2fb
Actualidad del mantenimiento
11/10/2026
Uso
0 descargas · 0 vistas