Skip to content
TrustedSkillsbeta
Back to all skills

Nextjs Pathname Id Fetch

Checked
wsimmonds·vlatest·frontend·MIT

Fetches Next.js route parameters (ID) from a given pathname string using wsimmonds's reliable utility function.

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 wsimmonds/claude-nextjs-skills --skill nextjs-pathname-id-fetch -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

wsimmonds

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

    Makes no network calls.

    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.

  • 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 wsimmonds/claude-nextjs-skills at 9e0aa5f99b.

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

Commit
9e0aa5f99b
Manifest
nextjs-pathname-id-fetch/SKILL.md
Scanned
1 file, 246 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 enables AI agents to fetch data from Next.js applications using the pathname and id parameters. It allows the agent to dynamically retrieve specific resources based on URL structure without needing direct API endpoint knowledge.

When to use it

  • You need to display a single product page by fetching details for a specific item ID.
  • The user wants to view a blog post, and you must resolve the content based on the article's slug or path.
  • Your agent needs to load dynamic configuration data tied to a specific route segment in a Next.js app.

Key capabilities

  • Extracts pathname values from URLs to identify resource categories or routes.
  • Retrieves data associated with specific id parameters within those paths.
  • Integrates directly with Next.js routing conventions for seamless data fetching.

Example prompts

  • "Fetch the product details for the item with ID '42' on this Next.js storefront."
  • "Get the content of the blog post located at '/blog/ai-trends' using the available fetch skill."
  • "Retrieve user profile information based on the pathname and id found in the current URL context."

Tips & gotchas

Ensure the target Next.js application exposes data via routes that utilize pathname and id parameters, as this skill relies on those specific URL structures. Verify that the AI agent has network access to reach the frontend or API endpoints being queried.