This repository was archived by the owner on Apr 19, 2026. It is now read-only.
docs(profile): rewrite org README with platform-neutral, verifiable copy#2
Merged
docs(profile): rewrite org README with platform-neutral, verifiable copy#2
Conversation
Rework the LeadMagic organization profile README so the rendered
github.com/LeadMagic page matches the current product positioning on
leadmagic.io, uses language we can stand behind, and steers clear of
claims about specific third-party platforms we do not operate.
Key changes:
- Lead with the current tagline ("The B2B Data API for AI Agents and
GTM Engineers") and the REST + CLI + MCP surface model used on the
marketing site.
- Remove references to "LinkedIn" and any phrasing that could imply we
scrape or index a specific social network. Use platform-neutral terms
like "B2B profile enrichment", "professional profile URLs", and
"direct-dial numbers", matching the public OpenAPI snapshot.
- Drop unverifiable marketing claims (99% accuracy hero stat, 95%
primary-inbox figures, 300% / 8x response-rate anecdotes, Fortune 500
branding, SOC 2 Certified badge, fabricated testimonials, fixed
monthly pricing tiers). Replace with neutral language and link to the
canonical pages (leadmagic.io, /docs, /pricing) that stay in sync.
- Point all doc links at the canonical leadmagic.io/docs host instead
of docs.leadmagic.io, which redirects.
- Fix mojibake (corrupt emoji in the feature grid header) and the
outdated copyright year (2025 -> 2026).
- Feature the public repos we actually maintain — leadmagic-openapi
and leadmagic-cursor-plugin — and the hosted MCP entrypoint,
including the public client-discovery endpoint at
mcp.leadmagic.io/clients.
- Cross-link the brand-impersonation guidance in
leadmagic-openapi/SECURITY.md so visitors who find a third-party
"LeadMagic" package have an authoritative allow-list to check.
- Keep the ASCII wordmark and the bootstrapped / customer-funded
framing, but cut superlatives and anything that implies claims we
have not publicly substantiated.
The repo-root README.md was the default `# .github` placeholder, which is what visitors see when they browse the repo directly. Replace it with a short, professional pointer that: - states this is a meta/community-health repository and not a product repo, and links out to the GitHub docs explaining what a `.github` repo is; - directs visitors looking for code to the two canonical public repos (leadmagic-openapi, leadmagic-cursor-plugin) and the current product docs / MCP endpoint / dashboard; - reinforces the editing convention (profile/README.md is the public org page) and cross-links the brand-impersonation allow-list in leadmagic-openapi/SECURITY.md so anyone about to submit a PR here sees the positioning rules before they start typing; - surfaces the security and support mailboxes. Included in the same PR as the profile rewrite because it is the same class of org-facing documentation and they should ship together.
Contributor
Author
|
Follow-up commit
Post-merge operational noteThis repo was previously archived — I unarchived it only to push this branch. Once this PR merges, running will re-archive it. Archiving does not affect how |
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Rewrite the LeadMagic organization profile README (
profile/README.md, which is what renders at github.com/LeadMagic) so the copy matches the current product positioning onleadmagic.io, uses language we can stand behind, and steers clear of claims about specific third-party networks we don't operate.The previous README leaned hard on unverifiable marketing numbers, referenced "LinkedIn enrichment" (which the current public API and website have already moved away from), and pointed to a
docs.leadmagic.iohost that redirects. This PR brings it into alignment with the way Marketing, Product, and the OpenAPI snapshot already describe LeadMagic.What changed
Positioning and voice
leadmagic.ioframes it today: one API key, three surfaces — REST, CLI, and hosted MCP.https://mcp.leadmagic.io/mcpand link to the canonical per-client install discovery athttps://mcp.leadmagic.io/clients.Language cleanup
leadmagic-openapiand the public docs.leadmagic.io,leadmagic.io/docs,leadmagic.io/pricing).Structural improvements
/pricing.leadmagic-openapi,leadmagic-cursor-plugin) so visitors don't have to guess whichLeadMagic/*repo is canonical.leadmagic-openapi/SECURITY.mdand thesecurity@leadmagic.iomailbox.��) in the old feature grid header.Rendered behaviour
This file is read from
profile/README.mdand becomes the org profile card at https://github.com/LeadMagic. GitHub will re-render it within a minute of merge.Operational note: this repo was previously archived. I unarchived it to push this branch. After this PR merges (and any follow-up tweaks land), feel free to re-archive — the profile README still renders while archived, writes are just blocked.
Secret / link safety
LinkedIn,scrape,SOC 2,Fortune,99%,95%,300%,8x— zero matches.leadmagic.io,mcp.leadmagic.io,app.leadmagic.io,github.com/LeadMagic/*,mailto:*@leadmagic.io, ortwitter.com/leadmagichqtarget.Test plan
git diff --stat— single-file change,profile/README.md, −194 / +82 lines.<div>blocks, no broken tables).shields.iotags and the three anchor URLs).Out of scope
README.md(still the default one-liner; can be a follow-up if we want the browse view to also have something).