Skip to content

NOTICKET Publish five public Apollo skills v0.2 - #9

Draft
SamuelTElliott wants to merge 7 commits into
apolloio:mainfrom
SamuelTElliott:codex/apollo-public-skills-v0.2-rebuild
Draft

NOTICKET Publish five public Apollo skills v0.2#9
SamuelTElliott wants to merge 7 commits into
apolloio:mainfrom
SamuelTElliott:codex/apollo-public-skills-v0.2-rebuild

Conversation

@SamuelTElliott

@SamuelTElliott SamuelTElliott commented Jul 13, 2026

Copy link
Copy Markdown

Purpose

Publish five portable Apollo workflow skills from one lean public source while retaining practical Claude Code, Claude Cowork, and Cursor setup guidance.

Scope

  • Exactly five public SKILL.md files: onboarding, analytics, enrich-lead, prospect, and sequence-load.
  • One compact inventory in catalog/skills.json.
  • Existing Claude and Cursor manifests advanced to 0.2.0.
  • Root README with Claude Code, Cowork, Cursor, OAuth, model-selection, credit, and troubleshooting guidance.
  • One dependency-free validator for inventory, frontmatter, tool references, encoding, release versions, Agent Skills description bounds, and public-hygiene exclusions.

Contract

  • apollo_organizations_lookup: merged free, shallow name/domain candidate and Apollo organization-ID resolution.
  • apollo_mixed_companies_search: filtered company prospecting, exactly one credit when results are returned, with immediate confirmation.
  • A missing free lookup is reported; it is never silently replaced with paid company search.
  • Enrichment, private-data reveal, record writes, enrollment, activation, and sending remain separate approval boundaries.
  • Apollo MCP remains usable without skills.

Deliberately excluded

No installer, public platform matrix, private Replit skill, internal evaluation artifact, customer data, credential, local path, generated package, lockfile, or unpublished evidence.

Team-owned registry PRs #5 and #10 are separate from this skills PR and overlap each other on server.json and glama.json. The owning team must choose one canonical registry name and publishing design; do not merge both as-is.

Verification

  • node scripts/validate-skills.mjs: pass; five public skills at catalog version 0.2.0.
  • Repository search: no stale lookup name or removed platform-catalog reference.
  • git diff --check: pass.
  • Changed index content is LF and contains no local-machine paths, private files, or platform-specific scripts.
  • Independent final review: no unresolved P0/P1/P2 findings.

Release gates

Leadgenie PR #97251 is merged. Do not publish v0.2.0 until apollo_organizations_lookup is deployed and verified on the production Apollo MCP surface with the agreed free lookup contract. MCP connectivity alone is not proof of skill delivery.

This PR supersedes closed PRs #7 and #8.

@kodem-security

kodem-security Bot commented Jul 13, 2026

Copy link
Copy Markdown

Kodem Security Scan Summary

Status Check Issues by Severity Link
⚠️ Warning Code Weakness Security Report 🟧 M: 2    Link to Check

Note: Kai marked some findings as likely false positives.

@orca-security-us orca-security-us Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Orca Security Scan Summary

Status Check Issues by priority
Passed Passed Infrastructure as Code high 0   medium 0   low 0   info 0 View in Orca
Passed Passed Secrets high 0   medium 0   low 0   info 0 View in Orca
Passed Passed Vulnerabilities high 0   medium 0   low 0   info 0 View in Orca

@SamuelTElliott
SamuelTElliott marked this pull request as ready for review July 14, 2026 16:32
@SamuelTElliott
SamuelTElliott marked this pull request as draft July 14, 2026 16:32
@SamuelTElliott SamuelTElliott changed the title Publish five public Apollo skills v0.2 source NOTICKET Publish five public Apollo skills v0.2 Jul 14, 2026
Comment thread README.md
In Claude Code, run:

```
/plugin marketplace add apolloio/apollo-mcp-plugin

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't our users need to know this command? Why do we remove it and all other instructions?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, and note it's not just removed, the new validator actively forbids adding these commands back (see my comment on validate-skills.mjs). Needs to be restored.

Use apollo_organizations_lookup for free name/domain resolution, keep filtered company search on the confirmed one-credit tool, restore verified Claude/Cowork/Cursor setup, and remove the volatile public platform matrix.

@marcus-gomes-v marcus-gomes-v left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really like the staged-approval safety model, separate gates for credits/reveal/writes/enroll/send is the right shape.

But requesting changes on three things: prospect depends on a tool that doesn't exist on production MCP yet, the install instructions were removed and the validator forbids adding them back, and analytics dropped its whole metric catalog with no end-to-end run as evidence.

Happy to approve once those land.

Comment thread catalog/skills.json
"summary": "Build a ranked search-first prospect list and gate enrichment, private data, and saves.",
"required_tools": [
"apollo_mixed_people_api_search",
"apollo_organizations_lookup",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't know if this tool exstis in the production MCP surface today — I checked the live tool list and there's no apollo_organizations_organization_lookup.

The PR body says we only publish after this contract exists, but nothing in the repo enforces that gate, what is the plan for this?

Comment thread README.md
In Claude Code, run:

```
/plugin marketplace add apolloio/apollo-mcp-plugin

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, and note it's not just removed, the new validator actively forbids adding these commands back (see my comment on validate-skills.mjs). Needs to be restored.

[/"visibility"\s*:\s*"private"/i, "private visibility"],
[/\bevals?\b/i, "evaluation artifact reference"],
[/\$ARGUMENTS/, "client-specific argument placeholder"],
[/\/apollo:/, "client-specific slash command"],

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This validator hard-bans /apollo: and /plugin in all public content, which means the install instructions Alexander asked about can never come back without editing the validator too?

Comment thread skills/analytics/SKILL.md

**Contact attributes**
`contact_stage_id`, `contact_label_ids`, `contact_owner_id`, `persona`, `person_title_unanalyzed`, `person_seniority`, `person_location_country`, `person_location_state`, `person_location_city`
Follow the parameter types exposed by the tools. For sequence paging, start with page 1 and a small page size. If the server rejects the visible schema, report a tool/schema blocker instead of retrying with guessed parameter shapes. If the report tool is absent, stop and do not invent data.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This drops the entire documented metric catalog (all the num_/percent_ names, group_by dimensions, filters: { user_ids: ["current"] }, sort rules). Was any skill actually run end-to-end against production MCP?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants