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 vendor check from supplied and authorized context.
--- name: vendor-check description: Check the status of existing agreements with a vendor across all connected systems — CLM, CRM, email, and document storage — with gap analysis and upcoming deadlines. Use when onboarding or renewing a vendor, when you need a consolidated view of what's signed and what's missing (MSA, DPA, SOW), or when checking for approaching expirations and surviving obligations. argument-hint: "[vendor name]" --- # /vendor-check -- Vendor Agreement Status > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Check the status of existing agreements with a vendor across all connected systems. Provides a consolidated view of the legal relationship. **Important**: This command assists with legal workflows but does not provide legal advice. Agreement status reports should be verified against original documents by qualified legal professionals. ## Invocation ``` /vendor-check [vendor name] ``` If no vendor name is provided, prompt the user to specify which vendor to check. ## Workflow ### Step 1: Identify the Vendor Accept the vendor name from the user. Handle common variations: - Full legal name vs. trade name (e.g., "Alphabet Inc." vs. "Google") - Abbreviations (e.g., "AWS" vs. "Amazon Web Services") - Parent/subsidiary relationships Ask the user to clarify if the vendor name is ambiguous. ### Step 2: Search Connected Systems Search for the vendor across all available connected systems, in priority order: #### CLM (Contract Lifecycle Management) -- If Connected Search for all contracts involving the vendor: - Active agreements - Expired agreements (last 3 years) - Agreements in negotiation or pending signature - Amendments and addenda #### CRM -- If Connected Search for the vendor/account record: - Account status and relationship type - Associated opportunities or deals - Contact information for vendor's legal/contracts team #### Email -- If Connected Search for recent relevant correspondence: - Contract-related emails (last 6 months) - NDA or agreement attachments - Negotiation threads #### Documents (e.g., Box, Egnyte, SharePoint) -- If Connected Search for: - Executed agreements - Redlines and drafts - Due diligence materials #### Chat (e.g., Slack, Teams) -- If Connected Search for recent mentions: - Contract requests involving this vendor - Legal questions about the vendor - Relevant team discussions (last 3 months) ### Step 3: Compile Agreement Status For each agreement found, report: | Field | Details | |-------|---------| | **Agreement Type** | NDA, MSA, SOW, DPA, SLA, License Agreement, etc. | | **Status** | Active, Expired, In Negotiation, Pending Signature | | **Effective Date** | When the agreement started | | **Expiration Date** | When it expires or renews | | **Auto-Renewal** | Yes/No, with renewal term and notice period | | **Key Terms** | Liability cap, governing law, termination provisions | | **Amendments** | Any amendments or addenda on file | ### Step 4: Gap Analysis Identify what agreements exist and what might be missing: ``` ## Agreement Coverage [CHECK] NDA -- [status] [CHECK/MISSING] MSA -- [status or "Not found"] [CHECK/MISSING] DPA -- [status or "Not found"] [CHECK/MISSING] SOW(s) -- [status or "Not found"] [CHECK/MISSING] SLA -- [status or "Not found"] [CHECK/MISSING] Insurance Certificate -- [status or "Not found"] ``` Flag any gaps that may be needed based on the relationship type (e.g., if there is an MSA but no DPA and the vendor handles personal data). ### Step 5: Generate Report Output a consolidated report: ``` ## Vendor Agreement Status: [Vendor Name] **Search Date**: [today's date] **Sources Checked**: [list of systems searched] **Sources Unavailable**: [list of systems not connected, if any] ## Relationship Overview **Vendor**: [full legal name] **Relationship Type**: [vendor/partner/customer/etc.] **CRM Status**: [if available] ## Agreement Summary ### [Agreement Type 1] -- [Status] - **Effective**: [date] - **Expires**: [date] ([auto-renews / does not auto-renew]) - **Key Terms**: [summary of material terms] - **Location**: [where the executed copy is stored] ### [Agreement Type 2] -- [Status] [etc.] ## Gap Analysis [What's in place vs. what may be needed] ## Upcoming Actions - [Any approaching expirations or renewal deadlines] - [Required agreements not yet in place] - [Amendments or updates that may be needed] ## Notes [Any relevant context from email/chat searches] ``` ### Step 6: Handle Missing Sources If key systems are not connected via MCP: - **No CLM**: Note that no CLM is connected. Suggest the user check their CLM manually. Report what was found in other systems. - **No CRM**: Skip CRM context. Note the gap. - **No Email**: Note that email was not searched. Suggest the user search their email for "[vendor name] agreement" or "[vendor name] NDA". - **No Documents**: Note that document storage was not searched. Always clearly state which sources were checked and which were not, so the user knows the completeness of the report. ## Notes - If no agreements are found in any connected system, report that clearly and ask the user if they have agreements stored elsewhere - For vendor groups (e.g., a vendor with multiple subsidiaries), ask whether the user wants to check a specific entity or the entire group - Flag any agreements that are expired but may still have surviving obligations (confidentiality, indemnification, etc.) - If an agreement is approaching expiration (within 90 days), highlight this prominently
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.