Skip to content
TrustedSkillsbeta
Back to all skills

Create Provider Package With Core

Checked
prefactordev·vlatest·backend·MIT

Helps with creation, packages as part of agent workflows workflows.

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 prefactordev/typescript-sdk --skill create-provider-package-with-core -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

prefactordev

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 prefactordev/typescript-sdk at a36ba5c3d1.

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

Scanned
2 files, 138 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 automates the creation of provider packages using a core template. It streamlines the process for developers building integrations or extensions, ensuring consistency and reducing boilerplate code. The resulting package includes necessary files and configurations to get started quickly with a new provider.

When to use it

  • You're developing a custom integration that requires its own packaged distribution.
  • You need to create multiple providers following a standardized structure.
  • You want to avoid manually setting up the initial project scaffolding for a new provider.
  • When building extensions or plugins for an existing platform.

Key capabilities

  • Automated package generation
  • Core template utilization
  • Standardized provider structure
  • Reduced boilerplate code

Example prompts

  • "Create a provider package named 'my-new-provider'."
  • "Generate a new provider package with the name 'payment-gateway'."
  • "Build a provider package using the core template and call it 'data-source'."

Tips & gotchas

  • Ensure you have the necessary dependencies installed before running this skill.
  • The "core" template defines the base structure; customization may require further adjustments after package creation.