# How to Update Dependencies in coreyhaines31/marketingskills: Zero-Dependency Guide

> Update dependencies in coreyhaines31/marketingskills with a simple git pull. This guide covers syncing the latest zero-dependency Node scripts for your project.

- Repository: [Corey Haines/marketingskills](https://github.com/coreyhaines31/marketingskills)
- Tags: how-to-guide
- Published: 2026-04-24

---

**The Marketing Skills repository contains no external package dependencies, so updating requires only a `git pull` to sync the latest zero-dependency Node scripts.**

The coreyhaines31/marketingskills repository is intentionally designed as a lightweight, zero-dependency toolkit for marketing automation. Since all CLI utilities are single-file Node scripts relying solely on the native `fetch` API (Node 18+), the repository contains no [`package.json`](https://github.com/coreyhaines31/marketingskills/blob/main/package.json), [`package-lock.json`](https://github.com/coreyhaines31/marketingskills/blob/main/package-lock.json), or `yarn.lock` files to maintain.

## Understanding the Zero-Dependency Architecture

According to [`tools/REGISTRY.md`](https://github.com/coreyhaines31/marketingskills/blob/main/tools/REGISTRY.md), every CLI tool in this repository is explicitly documented as having **no dependencies** and requiring only **Node 18+**. This architectural decision eliminates the traditional dependency update workflow entirely.

- **Single-file utilities**: Each CLI resides in `tools/clis/` as a standalone JavaScript file
- **Native `fetch`**: Scripts use the built-in global `fetch` API instead of external HTTP libraries like `axios` or `node-fetch`
- **No package manifests**: The absence of [`package.json`](https://github.com/coreyhaines31/marketingskills/blob/main/package.json) means no `npm install` or `npm update` commands are applicable

## How to Update the Repository

Since there are no external libraries to upgrade, "updating dependencies" translates to synchronizing your local copy with the upstream repository to receive the latest CLI versions, bug fixes, and skill definitions.

### Pull Latest Changes

Navigate to your local clone and fetch the newest commits from GitHub:

```bash
cd path/to/marketingskills
git pull origin main

```

This retrieves any updated scripts in `tools/clis/`, revised documentation, or new skill definitions added to the registry.

### Re-install Skills in Your Projects

If you use the skill installer to incorporate these tools into other projects, refresh your local skill files after pulling updates:

```bash
npx skills add coreyhaines31/marketingskills

```

Alternatively, using SkillKit:

```bash
npx skillkit install coreyhaines31/marketingskills

```

These commands replace outdated skill files in your project's `.agents/skills/` directory with the latest versions from the updated repository.

## Node Version Verification

Because the zero-dependency architecture relies on Node.js's native `fetch` API (introduced in Node 18), you must verify your runtime version before executing updated scripts:

```bash
node -v

```

The output must show **v18.0.0** or higher. Older Node versions lack the global `fetch` implementation and will throw runtime errors when executing tools like [`tools/clis/zoominfo.js`](https://github.com/coreyhaines31/marketingskills/blob/main/tools/clis/zoominfo.js).

## Syncing a Forked Repository

If you maintain a fork of coreyhaines31/marketingskills for customization, keep it synchronized with upstream changes:

1. Add the upstream remote (run once):

```bash
git remote add upstream https://github.com/coreyhaines31/marketingskills.git

```

2. Fetch and merge updates:

```bash
git fetch upstream
git merge upstream/main

# Or: git rebase upstream/main

```

This workflow ensures your custom modifications remain intact while incorporating upstream improvements to the zero-dependency CLIs.

## Summary

- **No dependency management**: The repository lacks [`package.json`](https://github.com/coreyhaines31/marketingskills/blob/main/package.json) by design; all tools use native Node.js APIs
- **Update via Git**: Run `git pull origin main` in your local clone to receive the latest scripts and documentation
- **Refresh skills**: Execute `npx skills add coreyhaines31/marketingskills` to update skill files in dependent projects
- **Node 18+ required**: Verify your runtime supports native `fetch` before running updated CLIs
- **Fork sync**: Use `git fetch upstream && git merge upstream/main` to maintain custom forks

## Frequently Asked Questions

### Does coreyhaines31/marketingskills use npm or yarn package management?

No. According to [`tools/REGISTRY.md`](https://github.com/coreyhaines31/marketingskills/blob/main/tools/REGISTRY.md), the repository explicitly maintains **no dependencies** and contains no [`package.json`](https://github.com/coreyhaines31/marketingskills/blob/main/package.json) file. All CLI tools in `tools/clis/` are self-contained Node.js scripts requiring only the built-in `fetch` API available in Node 18 and later.

### How do I know if I need to update my local copy of the repository?

If you forked or cloned the repository, run `git fetch origin` to check for new commits. Since there are no external libraries to version-lock, any upstream changes contain updated CLI logic, new skill definitions, or documentation improvements that require a simple `git pull` to synchronize.

### Why do the CLI scripts fail after updating the repository?

Execution failures typically indicate Node version incompatibility rather than missing dependencies. Verify your runtime with `node -v`. The scripts require Node 18 or newer to access the native `fetch` API; older versions will throw reference errors when attempting to call `fetch` without importing external libraries.

### Can I install specific versions of individual skills?

The repository does not support semantic versioning of individual components through npm. However, you may reference specific Git commits or tags when using installation tools. Check [`VERSIONS.md`](https://github.com/coreyhaines31/marketingskills/blob/main/VERSIONS.md) (if present) for version tracking of individual skills, or pin your clone to a specific Git ref to maintain stability across updates.