Skip to content
TrustedSkillsbeta
Back to all skills

Next Safe Route

Checked
mhbdev·vlatest·frontend·MIT

Calculates the safest driving route considering real-time hazards, weather, and user preferences for a smoother journey.

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 mhbdev/next-safe-route --skill next-safe-route -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

mhbdev

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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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 undeclared network calls: passed

    Only contacts known or declared hosts: registry.npmjs.org, github.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

    registry.npmjs.orgpackage registrygithub.comsource host

  • 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 mhbdev/next-safe-route at b55cdcecfd.

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

Commit
b55cdcecfd
Manifest
SKILL.md
Scanned
39 files, 11,115 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, next-safe-route, appears to be a component or library related to Next.js development. The provided source lacks specific details about its functionality, but it likely provides mechanisms for routing and potentially enhanced security within a Next.js application. It's designed for developers building web applications with the Next.js framework.

When to use it

  • You’re developing a Next.js application requiring custom or secure routing logic.
  • You need to implement role-based access control or other authentication checks on specific routes.
  • You want to simplify the process of protecting sensitive areas within your Next.js website.
  • You're building an internal dashboard or admin panel that requires restricted access.

Key capabilities

Based on the limited source information, it’s difficult to determine precise capabilities. However, we can infer:

  • Next.js integration
  • Routing functionality (likely custom routing)
  • Potential security features related to route access

Example prompts

Due to the lack of documentation, example prompts are speculative.

  • "Implement a secure route that requires user authentication."
  • "Create a protected dashboard accessible only to administrators."
  • "Configure role-based access control for specific routes in my Next.js application."

Tips & gotchas

This skill appears to be geared towards experienced Next.js developers. Familiarity with Next.js routing concepts and security best practices is likely required to effectively utilize this skill. Without further documentation, troubleshooting may require deeper code inspection.