Skills add-event-type
📦

add-event-type

Content revision r2 Safe ⚙️ External commands

Add Typed Events to React Feeds

Adding feed events often requires coordinated TypeScript, React, rendering, and WebSocket changes. This skill provides a focused workflow that follows existing project conventions.

Supports: Claude Codex Code(CC)
🥉 78 Bronze

Install with my Agent

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

Agent request
Review the Skillstore skill "add-event-type" from https://skillstore.io/skills/applelamps-add-event-type.md and its manifest at https://skillstore.io/api/skills/applelamps-add-event-type/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/applelamps-add-event-type.md Signed manifest GET /api/skills/applelamps-add-event-type/manifest Signed lockfile GET /api/skills/applelamps-add-event-type/lockfile

Test it

Using "add-event-type". Add a progress update event with a message and completion percentage.

Expected outcome:

  • Added a typed progress event with message and percentage fields.
  • Created a progress block that follows the existing feed styling.
  • Connected the event to feed rendering and prepared a mock validation case.

Using "add-event-type". Create a feed block for structured errors.

Expected outcome:

Added a structured error event and matching block, then connected it to the feed renderer using existing naming and styling conventions.

Using "add-event-type". Display search results received through WebSocket.

Expected outcome:

Extended the event union, added a search results block, updated message handling, and described a focused mock event test.

Security Audit

Safe
v9 • 7/23/2026 Open versioned report

All eight static findings are false positives caused by Markdown inline-code markers and fenced TypeScript examples. The skill contains no shell commands, executable backticks, prompt injection, or other semantic security concerns.

1
Files scanned
51
Lines analyzed
0
Review items
0
False positives ignored

Risk Factors

⚙️ External commands (8)
SKILL.md:9 SKILL.md:10 SKILL.md:14-19 SKILL.md:19-22 SKILL.md:22-24 SKILL.md:24-27 SKILL.md:27-35 SKILL.md:35-49
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 View Audit History →
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
Security Assessment

Copy report link

https://skillstore.io/skills/applelamps-add-event-type/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/applelamps-add-event-type/security.svg)](https://skillstore.io/skills/applelamps-add-event-type?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/applelamps-add-event-type?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/applelamps-add-event-type/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/applelamps-add-event-type.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

AppleLamps. (2026). add-event-type security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/applelamps-add-event-type/audits/9

BibTeX citation

@techreport{applelamps-applelamps-add-event-type-2026, author = {AppleLamps}, title = {add-event-type security audit report (audit version 9)}, institution = {Skillstore}, year = {2026}, number = {9}, url = {https://skillstore.io/skills/applelamps-add-event-type/audits/9}, 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: "add-event-type security audit report (audit version 9)" version: "unspecified" type: report authors: - name: "AppleLamps" date-released: "2026-07-23" url: "https://skillstore.io/skills/applelamps-add-event-type/audits/9" identifiers: - type: other value: "skillstore:applelamps-add-event-type:audit:9" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
85
Content
70
Community
91
Spec Compliance

What You Can Build

Display Search Results

Add a typed search result event and render its details in the frontend feed.

Surface Agent Progress

Create progress events that show ongoing agent work in a consistent React block.

Standardize Error Events

Introduce a structured error event and connect it to existing feed rendering.

Try These Prompts

Add a Basic Event 
Add a new [event_name] event type with fields for [field_list]. Follow the existing feed component patterns.
Add a Styled Event Block 
Create a [event_name] event and React block. Reuse nearby Tailwind styles and explain each changed file.
Connect a WebSocket Event 
Add [event_name] across TypeScript types, feed rendering, and WebSocket handling. Include a mock event for validation.
Extend the Feed End to End 
Inspect existing feed patterns, then add [event_name] with [field_list]. Update types, rendering, transport handling, and focused tests without using any.

Best Practices

  • Review nearby event interfaces and blocks before making changes.
  • Keep event names in snake case and React component names in PascalCase.
  • Test rendering with representative mock WebSocket events.

Avoid

  • Do not use any when a concrete event interface can be defined.
  • Do not add a union member without connecting its rendering path.
  • Do not introduce unrelated styles when existing Tailwind patterns are suitable.

Frequently Asked Questions

What files does this skill expect?
It expects event types and feed components in frontend/src/App.tsx, but the workflow can guide equivalent structures elsewhere.
Does it create the backend event?
No. It can update frontend handling for a backend event, but backend production remains project-specific.
Can it add WebSocket handling?
Yes. It directs updates to the message handler when the backend sends the new event type.
Does it support strict TypeScript?
Yes. The guardrails require complete types and prohibit any.
Will the new block match existing styles?
The workflow reviews nearby blocks and reuses existing Tailwind classes for visual consistency.
How should the new event be tested?
Send a representative mock event through the WebSocket path and verify its rendered block and fields.

Developer Details

Author

AppleLamps

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/AppleLamps/web-term/tree/main/.claude/skills/add-event-type

Ref

89edfdc710d0846129dcee6a929477b04f08052c

Maintenance freshness

7/24/2026

Usage

6 downloads · 214 views

File structure

📄 SKILL.md