Skip to content
TrustedSkillsbeta
Back to all skills

Velt Notifications Best Practices

Listed
velt-js·vlatest·other

Ensures velt-js notification implementation adheres to best practices for clarity, accessibility, and user experience.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add velt-js/agent-skills --skill velt-notifications-best-practices -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

velt-js

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: api.velt.dev, hooks.slack.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    api.velt.devundeclaredhooks.slack.comundeclared

    What it found (3 of 24)

    • skills/velt-notifications-best-practices/AGENTS.full.md:782contacts api.velt.dev
      const response = await fetch('https://api.velt.dev/v2/notifications/get', {
    • skills/velt-notifications-best-practices/AGENTS.full.md:810contacts api.velt.dev
      const response = await fetch('https://api.velt.dev/v2/notifications/update', {
    • skills/velt-notifications-best-practices/AGENTS.full.md:860contacts api.velt.dev
      const response = await fetch('https://api.velt.dev/v2/notifications/delete', {

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned velt-js/agent-skills at dcc5e5d192.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
dcc5e5d192
Manifest
skills/velt-notifications-best-practices/SKILL.md
Scanned
27 files, 4,727 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides best practices for implementing notifications within Velt applications. It focuses on ensuring notifications are clear, concise, and actionable, improving the user experience. The skill aims to guide developers in crafting effective notification strategies that align with Velt's design principles.

When to use it

  • When designing new features requiring user notifications.
  • During refactoring of existing notification systems within a Velt application.
  • To ensure consistency and adherence to established notification patterns across multiple components.
  • When troubleshooting confusing or ineffective user notifications.

Key capabilities

  • Provides guidance on clear and concise notification messaging.
  • Offers recommendations for actionable notification design.
  • Supports alignment with Velt's overall design principles.

Example prompts

  • "Suggest best practices for displaying a success message after a form submission in Velt."
  • "How should I structure an error notification to be helpful and not frustrating?"
  • “What are the recommended guidelines for using different notification types (e.g., banners, toasts) within a Velt application?”

Tips & gotchas

This skill assumes familiarity with the Velt framework and its component architecture. It's most effective when applied during the design or development phase rather than as a reactive fix to existing issues.