Research report · Run 6 · 26 September 2026
Lifecycle/email candidates under the low-access standard
This source inspection keeps one conditional, draft-only candidate for a future catalogue addition: Core Haines emails. It excludes RampStack email-sequences from this low-access catalogue pass.
Core Haines emails: keep only as a conditional draft
Source and package
- Selected source
- skills/emails/SKILL.md in
coreyhaines31/marketingskills. The repository names its builder as Corey Haines. The selected file currently identifies version2.0.0. - Directory
- The selected directory lists
SKILL.md,references/, andevals/. This run inspected the instruction file and directory listing, not the contents of the two subdirectories. - Provenance limit
- The link is a mutable
mainlink. This run did not establish a selected-file SHA or date.
Bounded first use
- Authorized input
- An owner supplies a non-personal description of a new-user segment, the product promise, and one approved destination URL.
- Draft output
- A five-email welcome-sequence brief in Markdown: trigger, goal, timing, exit conditions, subject, preview, body, CTA, and segment or conditions for each email.
- Not an implementation
- This is a reviewable draft, not an email-program configuration or send.
Data and tool stop
- Local context
- The selected file says to check local
.agents/product-marketing.mdand legacy alternatives if present. Do not load that material without data authorization. - Linked tools
- The file names a separate implementation-tools registry and email services. Do not follow that registry or use its integration routes for this candidate.
- Input surface
- Audience, trigger, goals, performance, and related-email context can be business-sensitive or customer-derived. This candidate uses no customer data.
Human boundary
- Verify
- An authorized person verifies every factual and product claim, CTA destination, audience or segment, timing, exit condition, consent basis, accessibility, and applicable legal and deliverability requirements.
- Approve separately
- That person separately approves any import, configuration, scheduling, test, publication, or send.
- Access statement
- The selected file does not state that a credential, account, connector, paid credit, named model, customer-system read, or send is required to produce the defined draft. This absence is not a guarantee about an installer, host, linked registry, model, future revision, or follow-on implementation.
The repository says its collection works with several agent hosts and documents CLI, plugin, clone/copy, submodule, and SkillKit routes. Those are maintainer statements only. No route was run, and this report makes no installation recommendation. The root README identifies the repository as MIT; the root LICENSE is the primary license text. This is not legal advice.
RampStack email-sequences: exclude
The selected RampStack file can produce a Markdown sequence, but it requests an audience or segment or list and technical provider constraints. Its inspected workflow directs the user to send a sequence to themself, configure triggers in an email-service provider, schedule broadcasts, and measure results. Those routes exceed the low-access, reviewable-first boundary. Do not add this skill from this run.
The file does not state a required credential, connector, paid credit, named model, or cost for drafting. That does not change the exclusion. The repository’s install, distribution, license, and source-stated security-process statements were not tested or verified.
Existing catalogue caveats are unchanged
This email-only work did not recheck or change the four Superamped selected-file provenance caveats. No selected-file SHA/date or tag finding has been established for Content Strategy, Competitor Discovery, Search Page Audit, or Ad Campaign Analyzer. Their stop before an install recommendation remains exactly as recorded in Run 5.
Source and testing boundary
This is source inspection only. No package, selected directory, reference file, installer, plugin command, host, or tool was installed, cloned, copied, executed, evaluated, modified, or tested. No credential, API key, account, connector, MCP server, email service provider, customer system, customer data, mailing list, recipient address, campaign data, local product-context file, email send, test email, scheduled email, publication, or other external action was used.
No security, privacy, permission, malware, compatibility, host-discovery, install behavior, accuracy, legal or compliance, consent, deliverability, accessibility, model or cost, marketing-performance, or outcome property was tested or established. Repository source and maintainer documentation are not evidence of those properties. The source-described output is a draft only; every external action remains owner approval work outside this report.
Sources: Core Haines emails source · Core Haines emails directory · Core Haines README · RampStack email-sequences source · RampStack README · RampStack LICENSE. Checked 26 September 2026 UTC.