Skills template-builder-ui

📦

template-builder-ui

Name: template-builder-ui
Author: sentdm

Content revision r1 Safe 🌐 Network access⚙️ External commands

Design Safer Sent Template Builder Interfaces

Template builders can drift from Sent contracts and expose unsafe submission flows. This skill guides precise editors, previews, validation, and review controls.

Supports: Claude Codex Code(CC)

📊 76 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "template-builder-ui" from https://skillstore.io/skills/sentdm-template-builder-ui.md and its manifest at https://skillstore.io/api/skills/sentdm-template-builder-ui/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sentdm-template-builder-ui.md Signed manifest GET /api/skills/sentdm-template-builder-ui/manifest Signed lockfile GET /api/skills/sentdm-template-builder-ui/lockfile

Test it

Using "template-builder-ui". Review a builder that saves and submits in one action.

Expected outcome:

Separate draft saving from review submission. Show a final confirmation with category, language, samples, overrides, buttons, warnings, and external-state impact.

Using "template-builder-ui". Assess a variable editor where users type placeholder syntax directly.

Expected outcome:

Replace direct placeholder editing with structured insertion. Update placeholders and entity records together, preserve samples, and report unmatched identifiers beside affected fields.

Using "template-builder-ui". Plan an RCS template preview with rich cards and SMS fallback.

Expected outcome:

Limit the current preview to text and four suggestion chips. Mark rich cards as roadmap-only and keep routing decisions outside the editor.

Security Audit

Safe

v1 • 9/2/2026 Open versioned report

All 27 static findings are false positives caused by ordinary prose, Markdown code spans, and product terminology. No executable commands, network calls, reconnaissance, keylogging behavior, prompt injection, or malicious intent were found.

Files scanned

270

Lines analyzed

Review items

False positives ignored

Risk Factors

🌐 Network access (1)

references/template-ui-wireflows.md:41

⚙️ External commands (21)

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sentdm-template-builder-ui/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sentdm-template-builder-ui/security.svg)](https://skillstore.io/skills/sentdm-template-builder-ui?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sentdm-template-builder-ui?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sentdm-template-builder-ui/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sentdm-template-builder-ui.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

sentdm. (2026). template-builder-ui security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sentdm-template-builder-ui/audits/1

BibTeX citation

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

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Design a New Template Editor

Plan fields, validation, previews, and submission controls around the Sent v3 contract.

Audit Payload Mapping

Check that interface fields serialize into supported template properties without unsupported top-level values.

Review Lifecycle Safety

Evaluate status handling, revision recovery, webhook updates, and explicit provider review confirmation.

Try These Prompts

Check a Basic Editor

Review this Sent template editor. Identify missing required fields, unsafe save behavior, and unclear validation feedback.

Design Channel Previews

Design SMS, WhatsApp, and RCS previews for this template flow. Include supported content, samples, accessibility, and channel-specific constraints.

Audit Variables and Buttons

Audit variable insertion, entity mapping, renumbering, button limits, authentication restrictions, and complete channel overrides in this builder.

Evaluate the Full Lifecycle

Evaluate this builder from draft creation through provider review. Cover payload mapping, sandbox validation, revisions, webhooks, unknown states, and failure recovery.

Best Practices

Keep one canonical draft aligned with the Sent definition contract.
Validate locally, then use sandbox validation before saving or submitting.
Preserve drafts, server responses, and revision history across errors and status changes.