Habilidades webask-integration-triage

📦

webask-integration-triage

Name: webask-integration-triage
Author: webaskio

Revisión del contenido r1 Seguro 📁 Acceso al sistema de archivos⚙️ Comandos externos

Diagnose WebAsk Integration Delivery Failures

Missing survey deliveries can leave teams without leads, notifications, or spreadsheet updates. This skill guides status checks, service-specific diagnosis, and supported retries after repairs.

Compatible con: Claude Codex Code(CC)

🥉 77 Bronce

Maintain this Skill? Claim it 🥉 77 Bronce

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 "webask-integration-triage" from https://skillstore.io/skills/webaskio-webask-integration-triage.md and its manifest at https://skillstore.io/api/skills/webaskio-webask-integration-triage/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

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.

Detalle Markdown GET /skills/webaskio-webask-integration-triage.md Manifest firmado GET /api/skills/webaskio-webask-integration-triage/manifest Lockfile firmado GET /api/skills/webaskio-webask-integration-triage/lockfile

Pruébalo

Usando "webask-integration-triage". Example scenario: Telegram logs show that the bot was removed from the group.

Resultado esperado:

Affected integration: Telegram.
Cause: the bot is no longer a member of the destination group.
Required action: return the bot to the group.
Retry status: no deliveries retried while the cause remains unresolved.

Usando "webask-integration-triage". Example scenario: the webhook delivery log shows an HTTP 500 response.

Resultado esperado:

Affected integration: the configured webhook.
Cause: the receiving endpoint returned a server error.
Required action: investigate and repair the receiving service before retrying the failed delivery.
Secret handling: keep masked authorization headers unchanged.

Usando "webask-integration-triage". Example scenario: the CRM integration is blocked by the current plan.

Resultado esperado:

Affected integration: CRM.
Cause: the integration is unavailable under the current plan.
Result: diagnosis stopped without changing settings or retrying delivery.

Auditoría de seguridad

Seguro

v1 • 29/9/2026 Abrir el informe versionado

All 13 static findings are false positives: relative documentation links and Markdown formatting do not establish traversal or shell execution. No evidence found of prompt injection, credential extraction, or unauthorized data transfer in the reviewed skill files. The workflow requires consent before enabling delivery and protects masked webhook secrets; external MCP implementations were not assessed.

Archivos escaneados

231

Líneas analizadas

Elementos de revisión

Falsos positivos ignorados

Factores de riesgo

📁 Acceso al sistema de archivos (1)

README.md:1

⚙️ Comandos externos (12)

SKILL.md:16 SKILL.md:18 SKILL.md:25 SKILL.md:26 SKILL.md:27 SKILL.md:36 SKILL.md:40 SKILL.md:41 SKILL.md:45 SKILL.md:50 SKILL.md:59 SKILL.md:60

La auditoría estática y semántica completada más reciente no detectó hallazgos de seguridad confirmados. Esto no demuestra que el skill no tenga efectos secundarios.

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.

Abrir el informe versionado

Copiar enlace del informe

https://skillstore.io/skills/webaskio-webask-integration-triage/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Insignia Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/webaskio-webask-integration-triage/security.svg)](https://skillstore.io/skills/webaskio-webask-integration-triage?utm_source=security_passport_badge)

Insignia HTML

<a href="https://skillstore.io/skills/webaskio-webask-integration-triage?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/webaskio-webask-integration-triage/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Tarjeta para insertar

<iframe src="https://skillstore.io/embed/skills/webaskio-webask-integration-triage.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

webaskio. (2026). webask-integration-triage security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/webaskio-webask-integration-triage/audits/1

Cita BibTeX

@techreport{webaskio-webaskio-webask-integration-triage-2026,
  author = {webaskio},
  title = {webask-integration-triage security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/webaskio-webask-integration-triage/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: "webask-integration-triage security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "webaskio"
date-released: "2026-09-29"
url: "https://skillstore.io/skills/webaskio-webask-integration-triage/audits/1"
identifiers:
  - type: other
    value: "skillstore:webaskio-webask-integration-triage:audit:1"
    description: "Skillstore immutable audit report identifier"

Puntuación de Skillstore

Por qué esta puntuación Confianza de la evidencia: Medio

Arquitectura

Mantenibilidad

Contenido

Comunidad

Cumplimiento de la especificación

Lo que puedes crear

Investigate Missing CRM Leads

Check survey integration status and Bitrix24 connectivity, then identify the account repair needed to restore access.

Restore Team Notifications

Review Telegram or MAX delivery failures, explain the required chat repair, and retry failed notifications after recovery.

Diagnose Webhook Delivery Errors

Inspect webhook status and receiver response codes, then retry a failed delivery after the endpoint is repaired.

Prueba estos prompts

Check a Missing Notification

Telegram notifications stopped for the survey named [survey name]. Confirm the survey and explain the cause without changing settings.

Investigate CRM Access

Check why survey [survey ID] no longer sends leads to Bitrix24. Inspect integration status and portal connectivity, then explain any required account repairs.

Recover Failed Messenger Deliveries

For survey [survey ID], verify that the Telegram failure is resolved. Retry failed notifications from [start date] to [end date] and report the result.

Triage Multiple Delivery Channels

Audit survey [survey ID] across CRM, Google Sheets, messengers, and webhooks. Separate configuration issues from receiver failures. Propose repairs without changing settings or replaying deliveries.

Mejores prácticas

Confirm the survey identity and inspect integration status before running deeper checks.
Resolve the underlying service failure before retrying a clearly scoped set of deliveries.
Obtain consent before enabling delivery and keep masked webhook credentials out of chat.

Evitar

Enabling a disabled integration without checking whether it was intentionally paused.
Repeating failed deliveries before repairing the underlying cause.
Requesting secret header values or overwriting webhook configuration merely to test access.