Skip to content
Back to search

hapi-kit

MarketplaceWorks with Claude CodeGitHub

Private skill kit for embedded B2B marketing work.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/centeredmktg--hapi-kit/badge.svg)](/listings/centeredmktg--hapi-kit)

HTML

<a href="/listings/centeredmktg--hapi-kit"><img src="/api/listings/centeredmktg--hapi-kit/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Install into a company workspace from a pinned tag, so what's in use matches what was disclosed:

git clone --branch v1.6.0 git@github.com:centeredmktg/hapi-kit.git ~/hapi-kit
claude plugin marketplace add ~/hapi-kit
claude plugin install hapi-kit@hapi-kit                        # all kit skills, user scope
claude plugin install superpowers@hapi-kit --scope project     # only in repos where you build
claude plugin install seo-suite@hapi-kit --scope project       # only in a site/SEO repo

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 36 lines
  1. {
  2. "name": "hapi-kit",
  3. "owner": {
  4. "name": "Danny Cox"
  5. },
  6. "description": "Private skill kit for embedded B2B marketing work.",
  7. "plugins": [
  8. {
  9. "name": "hapi-kit",
  10. "source": "./",
  11. "description": "Embedded-marketer skill kit (original skills)"
  12. },
  13. {
  14. "name": "superpowers",
  15. "description": "Public, MIT. Brainstorming, plan writing, plan execution, TDD, debugging. Pulled from upstream, pinned to v7.0.2.",
  16. "category": "development",
  17. "source": {
  18. "source": "url",
  19. "url": "https://github.com/obra/superpowers.git",
  20. "sha": "22f0b463e7a5e579904dd6211a520321035526f7"
  21. },
  22. "homepage": "https://github.com/obra/superpowers"
  23. },
  24. {
  25. "name": "seo-suite",
  26. "description": "Public, MIT. SEO, AEO and AI-search audits. Pulled from upstream, pinned to v2.4.2.",
  27. "category": "marketing",
  28. "source": {
  29. "source": "url",
  30. "url": "https://github.com/AgriciDaniel/claude-seo.git",
  31. "sha": "4b99de2f7de7e7d5247042e5fb5b4ea9368ef734"
  32. },
  33. "homepage": "https://github.com/AgriciDaniel/claude-seo"
  34. }
  35. ]
  36. }
README.md · README · 53 lines
  1. # hapi-kit
  2. A Claude Code plugin catalog: one plugin of 26 skills, plus pinned references to two public plugins, for an embedded B2B marketer: messaging, ABM, sales enablement, content QA, weekly review, developer checks, and a lightweight session worklog.
  3. The 18 original skills are Danny Cox's prior inventions, listed on Schedule B of his employee agreement. Bringing them into company work grants the company a non-exclusive license to use them as incorporated (clause (c)). Ownership stays with Danny. Skills added to the kit later, and third-party skills included under their own license, are listed separately in `MANIFEST.md`.
  4. ## The boundary (read before adding anything)
  5. | Belongs in this repo | Belongs in a company-owned repo |
  6. |---|---|
  7. | Generic method: skills that work for any B2B company | Anything company-specific: context, ICP, account lists, scoring weights, messaging, scripts against company systems |
  8. | Changes made on personal equipment, on personal time | Any change made on company equipment, company accounts, or company time |
  9. - **This repo flows one way.** Changes made inside company work stay in the company's repo, as a fork or copy. They never get merged back here.
  10. - **No company data here, ever.** No customer names, metrics, roadmap, credentials or exports.
  11. - **New skills need notice first.** Before using a skill that isn't in `MANIFEST.md` for company work, add it to the manifest and give the company written notice.
  12. ## Install
  13. Install into a company workspace from a pinned tag, so what's in use matches what was disclosed:
  14. ```bash
  15. git clone --branch v1.6.0 git@github.com:centeredmktg/hapi-kit.git ~/hapi-kit
  16. claude plugin marketplace add ~/hapi-kit
  17. claude plugin install hapi-kit@hapi-kit # all kit skills, user scope
  18. claude plugin install superpowers@hapi-kit --scope project # only in repos where you build
  19. claude plugin install seo-suite@hapi-kit --scope project # only in a site/SEO repo
  20. ```
  21. ## Public plugins (pulled from upstream)
  22. `superpowers` and `seo-suite` aren't copied into this repo. The catalog points at each upstream GitHub repo, pinned to a commit that has been reviewed:
  23. | Entry | Upstream | Pinned | Always-on cost |
  24. |---|---|---|---|
  25. | superpowers | github.com/obra/superpowers | v7.0.2 · 22f0b46 | ~2K tokens/session (session-start hook) plus skill list |
  26. | seo-suite | github.com/AgriciDaniel/claude-seo (listed as seo-suite because names starting with "claude-" are reserved) | v2.4.2 · 4b99de2 | ~4.5K tokens/session |
  27. To upgrade one: read the upstream diff since the pinned commit, then bump the `sha` in `.claude-plugin/marketplace.json` and tag a new version. Never point at a branch, because an unpinned upstream can change what runs on a company machine without anyone looking.
  28. Known issue in superpowers 7.0.2: the brainstorming "visual companion" (an optional local mockup server) had two medium findings in security review, a token-file reuse and a predictable /tmp path. Decline the offer to open a browser tab, or review upstream for a fix before using it.
  29. Then copy `workspace-template/` into the company-owned workspace repo and fill in `CLAUDE.md` and `context/company.md`. Copy `profile/about-danny.md` into that repo as `about-me.md`; the template CLAUDE.md imports it, so every session starts with it. The skills read `context/`, write to `outputs/`, and the session close writes to `worklog/`.
  30. ## Building infrastructure
  31. Use superpowers at project scope in the company's build repos: `brainstorming` → `writing-plans` → `executing-plans`, with TDD and systematic debugging alongside.
  32. ## Token notes
  33. - At rest, each skill costs only its description, about 2.2K tokens total for the 26 skills.
  34. - When a skill runs, its body loads: about 500–1,400 words. `humanizer` loads its full 4K-word pattern catalog only for long documents.
  35. - `/ok-i-love-you-goodbye` here is the lite version: one appended worklog entry and nothing else.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.