Main Scripts Defined in package.json for marketingskills: Complete Repository Analysis

The marketingskills repository does not contain a package.json file, meaning no npm scripts are defined in the traditional Node.js manifest. A repository-wide search confirms zero matches for package.json, redirecting users to alternative script locations in tools/clis/ and skill-specific scripts/ directories.

The marketingskills repository by coreyhaines31 takes an unconventional approach to JavaScript tooling. While most Node.js projects centralize commands in a root-level manifest, searching for the main scripts defined in package.json for marketingskills reveals that the file simply does not exist. This architectural choice eliminates standard npm workflows in favor of zero-dependency CLI scripts and decentralized automation.

Absence of package.json in the Repository Root

According to the source code file structure, a glob search for package.json at the repository root returned no results. This confirms the project is not structured as a Node.js package with centralized dependency management or script definitions.

Without this manifest file, standard commands like npm run build, npm test, or npm start are unavailable. The repository avoids the Node.js ecosystem's typical node_modules directory and version-locked dependency trees entirely.

Where Executable Scripts Actually Reside

While there are no main scripts defined in package.json for marketingskills, the project provides runnable automation through two documented pathways:

Zero-Dependency Node.js CLI Tools

As specified in AGENTS.md, the repository maintains standalone CLI scripts in the tools/clis/*.js directory. These files operate without external npm dependencies, eliminating the need for package installation before execution.

Run these tools directly using the Node.js runtime:

node tools/clis/example-script.js

Skill-Specific Script Directories

The CONTRIBUTING.md guidelines reference optional executable code located within scripts/ subdirectories inside individual skill folders. This pattern distributes automation logic across the codebase rather than centralizing all commands in a single root manifest.

Implications for Development Workflow

The lack of a package.json file means developers cannot rely on npm install to prepare the environment or npm run to execute tasks. Instead, the project assumes direct Node.js execution for the CLI tools stored in tools/clis/. This design keeps the repository lightweight and avoids dependency management overhead while still providing programmable interfaces for marketing skill automation.

Summary

• No package.json exists: A repository-wide glob search confirms the coreyhaines31/marketingskills project lacks this Node.js configuration file entirely.
• No npm scripts available: Consequently, there are no main scripts defined in package.json for marketingskills to document or execute via npm.
• CLI tools in tools/clis/: Zero-dependency Node.js scripts reside in tools/clis/*.js, as documented in AGENTS.md.
• Decentralized scripts: Optional automation exists in scripts/ directories within individual skill folders, per CONTRIBUTING.md guidelines.

Frequently Asked Questions

Does the marketingskills repository contain a package.json file?

No. According to the source code analysis, a comprehensive search for package.json in the coreyhaines31/marketingskills repository returned zero matches, confirming the file is absent from both the project root and all subdirectories.

Where are the main scripts defined if not in package.json?

The project places executable logic in two specific locations: zero-dependency Node.js CLI scripts under tools/clis/*.js (referenced in AGENTS.md), and optional scripts within scripts/ directories inside individual skill folders (mentioned in CONTRIBUTING.md).

How do I execute code in marketingskills without npm scripts?

Since no npm scripts exist, execute the zero-dependency CLI files directly with Node.js using commands like node tools/clis/script-name.js. These scripts require no npm install step because they do not rely on external packages defined in a manifest.

Why would an open-source project omit package.json entirely?

The marketingskills repository likely omits package.json to maintain zero-dependency tooling and eliminate Node.js package management complexity. This architectural decision keeps the project lightweight, avoids version conflicts, and ensures immediate executability of the CLI tools without dependency tree resolution.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}