Marketing Foundation
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
The tunnel uses the same cards as the catalogue. Browse only as deep as needed — or load a broad bundle immediately.
SEO, Sales, Agents or another broad area → one bundle call → work.
Read-only access to published skills. Default 8, maximum 10 skills / 120,000 characters.
Compact two-skill starter: clarify positioning and choose a lead magnet. Use Marketing Launch for the broader eight-skill go-to-market workflow.
Build an evidence-led marketing plan from ICP and competition through positioning, campaigns, growth and measurement.
Diagnose architecture and context, plan agent-team responsibilities, then organize project context and session handoffs. Memory and cost-runtime reviews remain outside this pack.
Review the journey from landing page and lead capture through registration, first value and transparent upgrades.
Plan a campaign, draft its channel content and review the work against actual brand guidance.
Prioritize an editorial roadmap and plan how to launch and distribute it across suitable channels.
Understand customer needs, compare competitors and plan a community around real member value.
Choose a relevant lead magnet, then draft a permission-based nurture journey with entry, suppression and exit rules.
Define the API contract, then plan how to observe its latency, failures and retries. Guidance and checklist; no production changes.
Profile a dataset, choose and interpret statistical methods, then validate calculations and conclusions before sharing.
Define the target account, prioritize buying signals, plan a human LinkedIn engagement routine and prepare evidence-led responses to buyer concerns.
Guides growth pulse from supplied and authorized context.
--- name: growth-pulse description: > Answers one question for an SMB owner — is the growth engine actually working? Pulls sales trend by channel, funnel conversion, campaign return, best and worst performing products, and customer sentiment from whatever is connected, then ends with the three growth actions worth taking this week. The growth-side twin of business-pulse, which covers the finance side. Use this whenever the owner asks how marketing or sales is performing, whether a campaign paid off, where leads are coming from, why the pipeline is stalling, which products are moving, or says anything like "is my marketing working," "growth check," "how's the funnel," or "where should I put my money next month." Reach for it even when the owner names a single channel rather than growth overall. allowed-tools: Read, WebFetch --- # Growth Pulse One page that answers whether the growth engine is working, and what to do about it this week. Owners describe pulling numbers from three dashboards and trying to find the story themselves. The story is the deliverable here — not the dashboards. ## Step 1 — Pull everything in parallel Dispatch all connector calls in a single batch. See `reference/data_sources.md` for the metric-to-tool mapping. Serial pulls turn this into a wait nobody sits through twice. - **HubSpot** — deals by stage, new contacts, lead source, win rate, cycle time, stalled deals - **PayPal, Stripe, Square** — revenue trend, transaction counts, refunds - **Shopify** — orders, SKU-level revenue, repeat purchase rate - **QuickBooks** — realized revenue, the number the books agree with - **TikTok Ads** — last week's spend, impressions, clicks, results, and cost per result per campaign, from the native connector (`report_integrated_get`, last 7 days against the prior 7), so paid spend sits beside the sales it claims to drive - **Mailchimp** — campaign, e-commerce, and audience-growth analytics, with revenue attribution on campaigns - **Gmail or Microsoft 365** — inbound inquiry volume and response times - **Public reviews** — recent ratings and review text, via web research If a source errors or is missing, record it and move on. This skill is designed to say something useful on one connector and something excellent on six. **Zero connectors is a supported path.** Ask for exports — a CRM deal export, a sales report, an ads performance CSV — and build the same pulse from files. Say it plainly rather than stalling. ## Step 2 — Compute the five views Read `reference/thresholds.md` for the cutoffs. Compute each view and assign it a status. 1. **Channel trend** — revenue by channel this period versus last, and versus the same period last year where available 2. **Funnel conversion** — leads in, qualified, opportunities, won; the conversion rate between each step and where the biggest drop-off sits 3. **Campaign return** — spend versus attributed revenue per campaign, and cost per lead 4. **Product performance** — top three and bottom three by revenue and by growth rate 5. **Customer sentiment** — recent review scores, review themes, disputes, churn signals A view with no data gets marked "n/a" and named in the appendix. It does not silently vanish. ## Step 3 — Find the actual story This is where the skill earns its keep. Five views on their own are still a dashboard. The job is to connect them. The connections that matter most: - **Spend rising while cost per lead rises** means the channel is saturating, not scaling - **Strong lead volume with falling win rate** points at lead quality or response speed, not at marketing - **One product carrying the whole trend** means the growth is more fragile than the total suggests - **Sentiment dropping while revenue holds** is the early warning that shows up in revenue two months later - **A stage where the funnel drops off sharply** is usually worth more than any new campaign Look for the single sentence that explains the period. Lead with it. ## Step 4 — Write the three actions Every pulse ends with exactly three actions. Not five, not a list of everything noticed. Each action needs three things or it isn't an action: - **What to do** — specific enough to start today - **Why** — the number from this pulse that justifies it - **What it's worth** — the rough size of the opportunity or the risk Rank them by size of impact, not by ease. Owners can decide what's easy; only this pulse can tell them what's big. If the honest answer is that nothing needs to change, say that. A pulse that manufactures three actions every week trains the owner to ignore them. ## Step 5 — Compose Use the exact structure in `reference/output_template.md`. Include only sections with real data. Writing rules: - Numbers lead, words follow. Not "paid social performed well" — "paid social drove 41 leads at USD 18 each, down from USD 31 last month." - Every number carries its comparison. A figure with no baseline is a missed insight. - Name the specific campaign, product, channel, or customer. "Some campaigns underperformed" is unusable. - No marketing vocabulary the owner doesn't use. Not "top of funnel velocity" — "how many new leads came in and how fast." - If a section has nothing worth saying, write "No material change" and move on. ## Step 6 — Deliver the pulse page Alongside the chat pulse — additive, never a replacement — deliver the full pulse per the owner's stored output preference — never default to a markdown file. Check the `## Business context` block's `Output preference` (shared style guide rule, `../../shared/artifact-style.md`): - **Visual artifact (the default):** render the pulse as an HTML page in the house style. Each of the five views gets a panel; revenue trend, cost per lead, and win rate are stat tiles with their comparison as the context line; campaign return and product performance are tables with tabular-nums spend and revenue columns; each view's status becomes a status pill (good, warn, critical, or n/a in plain text); the three actions close the page in their own panel, ranked. - **docx / md / notion / canva preference:** deliver the same content in that form — a DOCX or markdown file, a Notion page created via the connector (named destination, never overwriting), or a Canva Doc created via the Canva connector (a new design each run, named with the date; tables become lists); fall back to the visual artifact if Notion or Canva is not connected — and say that is why. - **Best for skill:** use the visual artifact — five views compare best side by side on one screen. ## Step 7 — Offer to save, once After presenting, offer once to save the pulse as a file or post it to Slack. Posting to Slack is an outward write, so it only happens on that explicit yes — the offer is the approval gate. If yes, do it. If no or no response, move on. Do not ask twice. Then close with what the pulse found in one line, plus the single most relevant next step and at most two others nearby: - If the actions point at content or promotion: "what should I promote" runs `content-strategy`. - If the funnel is the problem: "fill my funnel" runs `/grow-pipeline`. - For the finance-side twin: "how's the business doing" runs `business-pulse`. Max three offers. Never repeat an offer the owner declined this session. ## Scope variants Owners often want a slice rather than the whole pulse: - **"How did the campaign do"** — campaign return only, plus the sentiment check - **"How's the pipeline"** — funnel conversion and stalled deals only - **"What's selling"** — product performance only - **"Are we getting reviews"** — sentiment only - **"Where should I spend next month"** — channel trend and campaign return, with the three actions weighted toward budget Give them the slice they asked for. Don't force the full pulse on a narrow question. ## What not to do - **Do not ask permission before pulling data.** The skill was invoked. Run it. - **Do not invent attribution.** If a campaign's revenue can't be traced, say the attribution is unavailable rather than assigning revenue on a guess. Fake attribution has moved real budgets. - **Do not report CRM forecast value as revenue.** Deal values are hopes; invoices are facts. Label which is which. - **Do not double-count across sources.** A Shopify order settled in Stripe is one sale. Pick one revenue source and name it. - **Do not double-count inside one source.** The sales-by-customer summary returns both a parent summary row and a separate total row for the same customer. Filter rows marked as totals before you rank customers or compute concentration, or the same customer lands in the list twice and the concentration figure comes out too high. - **Do not manufacture urgency.** If growth is steady, the pulse should read as steady. - **Do not read expenses or margin from the QuickBooks P&L summary.** Total the rows (`../../shared/quickbooks-report-traps.md`, Trap 2). ## Reference files - `reference/data_sources.md` — connector to metric mapping, with fallbacks - `reference/thresholds.md` — status cutoffs for each of the five views - `reference/output_template.md` — exact output structure - `reference/gotchas.md` — the failure modes that produce confidently wrong growth advice ## Using a tool that isn't listed The connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer `build-connector` — it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.
Use for the stated task with user-supplied, authorized business context.
This source can refer to connectors, files, accounts, or related skills. They are not bundled, connected, or authorized by this catalog entry. Keep findings tied to supplied evidence.
Use the skill below for [TASK]. Ask for missing context, distinguish facts from assumptions, and do not connect accounts, send messages, or make external changes unless the user explicitly requests and authorizes them.
Automatic connector use, account access, sending, publishing, record changes, or claims unsupported by supplied evidence.
M11 added routing metadata, source attribution, integrity tracking and explicit boundaries around connectors and external actions. The original Apache-2.0 skill is retained unchanged.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Syntax-file, code seperations,code vault integeted with css definition.
Pre-recordec, pre-tested, elements to capture elements into Packeted-User-Relations to capture - [
pre-requisites, statements, recorded-cams
, cams-data
, data, input()
]
Copy the text below, then paste it into your chat.