# What Are the Main Directories in the MarketingSkills Project? > Explore the main directories in the MarketingSkills project. Understand the purpose of .claude-plugin/, .github/, and tools/ for organizing metadata, automation, and core tooling. - Repository: [Corey Haines/marketingskills](https://github.com/coreyhaines31/marketingskills) - Tags: getting-started - Published: 2026-04-24 --- **The MarketingSkills repository organizes its codebase into three primary directories—`.claude-plugin/`, `.github/`, and `tools/`—that cleanly separate plugin metadata, GitHub automation assets, and the core marketing tooling.** The `coreyhaines31/marketingskills` repository provides a structured collection of zero-dependency CLI tools and integration guides for marketing platforms. Understanding the **main directories in the MarketingSkills project** reveals how the codebase isolates configuration, automation, and functional logic into a modular, maintainable architecture. ## Top-Level Directory Structure The repository root organizes all content into three functional buckets. This separation ensures that plugin manifests, CI configuration, and actual marketing tools remain independent and easy to navigate. ### .claude-plugin/ The `.claude-plugin/` directory houses the Claude Code plugin manifest that makes the entire skill set installable as a plugin. This folder contains the [`marketplace.json`](https://github.com/coreyhaines31/marketingskills/blob/main/marketplace.json) file, which enables users to add the repository as a plugin with a single command within Claude Code environments. According to the source code, this directory bridges the repository with AI assistant integrations, keeping plugin-specific metadata isolated from the actual tooling logic. ### .github/ The `.github/` directory stores GitHub-specific configuration and automation assets. This includes continuous integration scripts, issue templates, funding information, and workflow definitions. For example, the repository includes [`.github/scripts/sync-skills.js`](https://github.com/coreyhaines31/marketingskills/blob/main/.github/scripts/sync-skills.js), a synchronization script that likely manages how skills are indexed or deployed. Keeping these assets in a dedicated folder ensures that repository automation does not clutter the core tool implementations. ### tools/ The **`tools/`** directory serves as the functional heart of the repository. It contains the registry of marketing skills, integration guides, and zero-dependency CLI wrappers. According to the source analysis, this directory is further subdivided into three critical subfolders: - **[`tools/REGISTRY.md`](https://github.com/coreyhaines31/marketingskills/blob/main/tools/REGISTRY.md)** – The master index that enumerates every available tool and its capabilities. - **`tools/integrations/`** – Markdown documentation providing step-by-step configuration guides for third-party marketing services. - **`tools/composio/`** – Documentation for the Composio integration layer that wraps OAuth-heavy APIs. - **`tools/clis/`** – Individual JavaScript CLI wrappers that provide direct, programmable access to marketing APIs. ## Deep Dive into the tools/ Directory Since the `tools/` directory contains the actual marketing functionality, its internal structure merits detailed examination. ### tools/integrations/ This subdirectory stores Markdown guides for configuring each marketing technology integration. Files like [`tools/integrations/ga4.md`](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/ga4.md) provide platform-specific setup instructions, authentication requirements, and usage patterns. The documentation here targets platforms such as Google Analytics 4 (GA4), HubSpot, Meta Ads, and ZoomInfo. ### tools/composio/ The `tools/composio/` folder contains documentation explaining how Composio wraps complex, OAuth-heavy APIs into a simpler MCP (Model Context Protocol) layer. This integration layer abstracts away authentication complexity, making it easier to connect with services that traditionally require intricate handshake protocols. ### tools/clis/ The `tools/clis/` subdirectory provides ready-to-run, zero-dependency Node.js scripts that interact directly with marketing APIs. Each file represents a standalone CLI tool: - [`tools/clis/ga4.js`](https://github.com/coreyhaines31/marketingskills/blob/main/tools/clis/ga4.js) – Interfaces with Google Analytics 4. - [`tools/clis/zoominfo.js`](https://github.com/coreyhaines31/marketingskills/blob/main/tools/clis/zoominfo.js) – Connects to ZoomInfo data services. - [`tools/clis/mailchimp.js`](https://github.com/coreyhaines31/marketingskills/blob/main/tools/clis/mailchimp.js) – Manages Mailchimp email marketing operations. These scripts require no external dependencies, making them portable and reliable across different execution environments. ## Root-Level Configuration Files Outside the three main directories, the repository root contains essential project metadata. Files such as [`README.md`](https://github.com/coreyhaines31/marketingskills/blob/main/README.md), `LICENSE`, and [`AGENTS.md`](https://github.com/coreyhaines31/marketingskills/blob/main/AGENTS.md) provide overall documentation, licensing terms, and developer guidance. This flat structure at the root level follows standard open-source conventions while keeping the specialized tooling nested within the `tools/` hierarchy. ## Summary The **main directories in the MarketingSkills project** create a clear separation of concerns: - **`.claude-plugin/`** isolates the Claude Code plugin manifest ([`marketplace.json`](https://github.com/coreyhaines31/marketingskills/blob/main/marketplace.json)) required for AI assistant integration. - **`.github/`** contains automation scripts (such as [`.github/scripts/sync-skills.js`](https://github.com/coreyhaines31/marketingskills/blob/main/.github/scripts/sync-skills.js)) and workflow configuration. - **`tools/`** houses the core functionality, including the registry ([`tools/REGISTRY.md`](https://github.com/coreyhaines31/marketingskills/blob/main/tools/REGISTRY.md)), integration guides (`tools/integrations/`), Composio documentation (`tools/composio/`), and executable CLI scripts (`tools/clis/`). This architecture separates metadata, automation, and functional tooling, making the repository easy to extend and consume. ## Frequently Asked Questions ### What is the purpose of the .claude-plugin directory? The `.claude-plugin/` directory contains the [`marketplace.json`](https://github.com/coreyhaines31/marketingskills/blob/main/marketplace.json) manifest file that registers the repository as an installable plugin for Claude Code. This allows users to add the entire MarketingSkills toolkit to their Claude Code environment with a single command, making the skills discoverable and accessible within the AI assistant interface. ### How does the tools/clis/ directory work? The `tools/clis/` directory contains zero-dependency JavaScript files that serve as standalone command-line interfaces to marketing APIs. Each file, such as [`tools/clis/ga4.js`](https://github.com/coreyhaines31/marketingskills/blob/main/tools/clis/ga4.js) or [`tools/clis/mailchimp.js`](https://github.com/coreyhaines31/marketingskills/blob/main/tools/clis/mailchimp.js), wraps a specific service's API in a runnable Node.js script that requires no package installation, enabling immediate execution across different systems. ### What marketing platforms are supported in the integrations folder? The `tools/integrations/` directory provides configuration guides for major marketing platforms including Google Analytics 4 (GA4), HubSpot, Meta Ads, ZoomInfo, and Mailchimp. Each platform has a dedicated Markdown file (e.g., [`tools/integrations/ga4.md`](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/ga4.md)) detailing authentication steps and implementation patterns. ### Where is the complete tool registry documented? The complete enumeration of all available tools and their capabilities is documented in [`tools/REGISTRY.md`](https://github.com/coreyhaines31/marketingskills/blob/main/tools/REGISTRY.md) at the root of the `tools/` directory. This file serves as the master index that lists every CLI script, integration guide, and Composio wrapper available in the repository, providing a single source of truth for the project's capabilities.