← KensoCONTENT HISTORY

Update to Kenso

Snapshot Nov 3, 2026 · 12:13 UTC · version 1.3.4

Collection source: downloaded plugin package.

WHAT CHANGED

Payment or plan references changed

Full description — Now says: Get oriented in a connected Kenso workspace - see the campaigns and where each one stands, then learn what Kenso can help with from the chat, area by area,...

Observed in published text. Live prices and checkout terms have not been verified by this change.

Save Kenso and check future changes in Following.

Up to 10 plugins free · no card required.

All fields and original values.

Full description

Before

Oct 24, 2026 · 13:53 UTC

Get oriented in a connected Ken workspace - see the campaigns, leads, sequences and blocklist, and learn what Ken can do from the chat.

After

Nov 3, 2026 · 12:13 UTC

Get oriented in a connected Kenso workspace - see the campaigns and where each one stands, then learn what Kenso can help with from the chat, area by area, with one example ask each.

Skill instructions

Before

Oct 24, 2026 · 13:53 UTC

Ken workspace - see the campaigns, leads, sequences and blocklist, and learn what Ken can do from the chat. # Get started with Ken Ken runs B2B outbound: cold email campaigns, their leads, their email sequences and the replies they get. ...

After

Nov 3, 2026 · 12:13 UTC

Kenso workspace - see the campaigns and where each one stands, then learn what Kenso can help with from the chat, area by area, with one example ask each. # Get started with Kenso Kenso runs B2B outbound: cold email campaigns to business...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,26 +1,34 @@
 ---
 name: get-started
-description: Get oriented in a connected Ken workspace - see the campaigns, leads, sequences and blocklist, and learn what Ken can do from the chat.
+description: Get oriented in a connected Kenso workspace - see the campaigns and where each one stands, then learn what Kenso can help with from the chat, area by area, with one example ask each.
 ---
 
-# Get started with Ken
+# Get started with Kenso
 
-Ken runs B2B outbound: cold email campaigns, their leads, their email sequences and the replies they get. This skill orients a newly connected user.
+Kenso runs B2B outbound: cold email campaigns to business contacts, their leads, their email sequences and the replies they get, plus the inboxes, accounts, meetings, pages and workflows around them. This skill orients a newly connected user, then shows what else Kenso can help with here.
 
 ## Steps
 
 1. Call `list_workspaces`. If it returns more than one workspace, show their names and ask which one to work in, then pass that workspace's id as workspace_id on every later call. With one workspace, skip this and leave workspace_id out.
-2. Call `list_campaigns` and summarize each campaign in one line: name, status (draft, active, paused, completed) and whether sending has started.
-3. If there is at least one campaign, offer three next steps the user can ask for, for example:
-   - "Show me the leads in <campaign name>."
-   - "Show me the email sequence for <campaign name>."
-   - "Add <domain> to my blocklist."
-   - "Which campaigns got the most replies this month?"
-4. If there are no campaigns, say so and explain that campaigns are created in the Ken app at https://app.ken.so or by asking here, for example "Create a draft campaign called Q1 agency owners."
+2. Call `list_campaigns` and summarize each campaign in one line: name, status (draft, active, paused, completed) and whether sending has started. If there are no campaigns, say so and explain that campaigns are created in the Kenso app at https://app.ken.so or by asking here, for example "Create a draft campaign called Q1 agency owners."
+3. Offer what Kenso can help with, one line per area with its example ask. Where an ask says <campaign name>, use a real campaign from step 2, or leave that ask out when there is none.
+   - **Campaigns and replies**: "Why did replies drop on <campaign name>, and what should I change?"
+   - **Workspace setup**: "Please set up my workspace."
+   - **Domains and inboxes**: "Help me set up the inboxes I send from."
+   - **Deliverability**: "Bounces are up. Are my domains and inboxes healthy?"
+   - **Accounts and pipeline**: "Which deals in my pipeline are stuck, and what is the next step on each?"
+   - **Meetings**: "Prep me for my next sales meeting."
+   - **Studio**: "Help me plan a Studio page for my target accounts."
+   - **Workflows**: "Help me plan a workflow that qualifies each new lead and flags the good ones."
+4. Only when step 2 listed a campaign, also offer a quick look at one of them, with its real name in the ask: "Show me the leads in <campaign name>." or "Show me the email sequence for <campaign name>."
+5. When the user picks an area, follow the Kenso skill for that job. If its text is not already in the conversation, `load_ken_skill` returns it by name.
+
+Some steps happen only in the Kenso app, such as connecting a mailbox, building a Studio template or a workflow, and changing a deal. The skill for that job links the page in the Kenso app (https://app.ken.so) where the user takes that step. Say so plainly; never claim a step was done here when the user has to do it in the app.
 
 ## Rules
 
 - Work only in the workspace the user picked. Use only ids `list_workspaces` returned; do not guess workspace or client IDs. When the user names another of their workspaces, switch workspace_id to it.
 - Ask the user to confirm before any action that sends email, starts or resumes a campaign, or deletes data. Drafts, reads and blocklist additions do not need extra confirmation.
-- Ken does not change plans, buy credits or process payments from the chat. Billing is managed by a workspace admin in the Ken app.
+- Kenso is for outreach to people in their business roles. Honor opt-outs: when someone asks not to be contacted, add them to the blocklist with `add_blocklist_entry`.
+- Kenso does not change plans, buy credits or process payments from the chat. Billing is managed by a workspace admin in the Kenso app.
 - Report tool errors in plain words and suggest the next step. Do not retry a failed write more than once.
Full technical diff · 2 changed fields

changed /description

BEFORE
"Get oriented in a connected Ken workspace - see the campaigns, leads, sequences and blocklist, and learn what Ken can do from the chat."
AFTER
"Get oriented in a connected Kenso workspace - see the campaigns and where each one stands, then learn what Kenso can help with from the chat, area by area, with one example ask each."

changed /skill_md_contents

BEFORE
"---\nname: get-started\ndescription: Get oriented in a connected Ken workspace - see the campaigns, leads, sequences and blocklist, and learn what Ken can do from the chat.\n---\n\n# Get started with Ken\n\nKen runs B2B outbound: cold email campaigns, their leads, their email sequences and the replies they get. This skill orients a newly connected user.\n\n## Steps\n\n1. Call `list_workspaces`. If it returns more than one workspace, show their names and ask which one to work in, then pass that workspace's id as workspace_id on every later call. With one workspace, skip this and leave workspace_id out.\n2. Call `list_campaigns` and summarize each campaign in one line: name, status (draft, active, paused, completed) and whether sending has started.\n3. If there is at least one campaign, offer three next steps the user can ask for, for example:\n   - \"Show me the leads in <campaign name>.\"\n   - \"Show me the email sequence for <campaign name>.\"\n   - \"Add <domain> to my blocklist.\"\n   - \"Which campaigns got the most replies this month?\"\n4. If there are no campaigns, say so and explain that campaigns are created in the Ken app at https://app.ken.so or by asking here, for example \"Create a draft campaign called Q1 agency owners.\"\n\n## Rules\n\n- Work only in the workspace the user picked. Use only ids `list_workspaces` returned; do not guess workspace or client IDs. When the user names another of their workspaces, switch workspace_id to it.\n- Ask the user to confirm before any action that sends email, starts or resumes a campaign, or deletes data. Drafts, reads and blocklist additions do not need extra confirmation.\n- Ken does not change plans, buy credits or process payments from the chat. Billing is managed by a workspace admin in the Ken app.\n- Report tool errors in plain words and suggest the next step. Do not retry a failed write more than once.\n"
AFTER
"---\nname: get-started\ndescription: Get oriented in a connected Kenso workspace - see the campaigns and where each one stands, then learn what Kenso can help with from the chat, area by area, with one example ask each.\n---\n\n# Get started with Kenso\n\nKenso runs B2B outbound: cold email campaigns to business contacts, their leads, their email sequences and the replies they get, plus the inboxes, accounts, meetings, pages and workflows around them. This skill orients a newly connected user, then shows what else Kenso can help with here.\n\n## Steps\n\n1. Call `list_workspaces`. If it returns more than one workspace, show their names and ask which one to work in, then pass that workspace's id as workspace_id on every later call. With one workspace, skip this and leave workspace_id out.\n2. Call `list_campaigns` and summarize each campaign in one line: name, status (draft, active, paused, completed) and whether sending has started. If there are no campaigns, say so and explain that campaigns are created in the Kenso app at https://app.ken.so or by asking here, for example \"Create a draft campaign called Q1 agency owners.\"\n3. Offer what Kenso can help with, one line per area with its example ask. Where an ask says <campaign name>, use a real campaign from step 2, or leave that ask out when there is none.\n   - **Campaigns and replies**: \"Why did replies drop on <campaign name>, and what should I change?\"\n   - **Workspace setup**: \"Please set up my workspace.\"\n   - **Domains and inboxes**: \"Help me set up the inboxes I send from.\"\n   - **Deliverability**: \"Bounces are up. Are my domains and inboxes healthy?\"\n   - **Accounts and pipeline**: \"Which deals in my pipeline are stuck, and what is the next step on each?\"\n   - **Meetings**: \"Prep me for my next sales meeting.\"\n   - **Studio**: \"Help me plan a Studio page for my target accounts.\"\n   - **Workflows**: \"Help me plan a workflow that qualifies each new lead and flags the good ones.\"\n4. Only when step 2 listed a campaign, also offer a quick look at one of them, with its real name in the ask: \"Show me the leads in <campaign name>.\" or \"Show me the email sequence for <campaign name>.\"\n5. When the user picks an area, follow the Kenso skill for that job. If its text is not already in the conversation, `load_ken_skill` returns it by name.\n\nSome steps happen only in the Kenso app, such as connecting a mailbox, building a Studio template or a workflow, and changing a deal. The skill for that job links the page in the Kenso app (https://app.ken.so) where the user takes that step. Say so plainly; never claim a step was done here when the user has to do it in the app.\n\n## Rules\n\n- Work only in the workspace the user picked. Use only ids `list_workspaces` returned; do not guess workspace or client IDs. When the user names another of their workspaces, switch workspace_id to it.\n- Ask the user to confirm before any action that sends email, starts or resumes a campaign, or deletes data. Drafts, reads and blocklist additions do not need extra confirmation.\n- Kenso is for outreach to people in their business roles. Honor opt-outs: when someone asks not to be contacted, add them to the blocklist with `add_blocklist_entry`.\n- Kenso does not change plans, buy credits or process payments from the chat. Billing is managed by a workspace admin in the Kenso app.\n- Report tool errors in plain words and suggest the next step. Do not retry a failed write more than once.\n"
Full snapshot data
{
  "description": "Get oriented in a connected Kenso workspace - see the campaigns and where each one stands, then learn what Kenso can help with from the chat, area by area, with one example ask each.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Get oriented in a connected Kenso workspace - see the campaigns and where each one stands, then learn what Kenso can help with from the chat, area by area, with one example ask each.\n---\n\n# Get started with Kenso\n\nKenso runs B2B outbound: cold email campaigns to business contacts, their leads, their email sequences and the replies they get, plus the inboxes, accounts, meetings, pages and workflows around them. This skill orients a newly connected user, then shows what else Kenso can help with here.\n\n## Steps\n\n1. Call `list_workspaces`. If it returns more than one workspace, show their names and ask which one to work in, then pass that workspace's id as workspace_id on every later call. With one workspace, skip this and leave workspace_id out.\n2. Call `list_campaigns` and summarize each campaign in one line: name, status (draft, active, paused, completed) and whether sending has started. If there are no campaigns, say so and explain that campaigns are created in the Kenso app at https://app.ken.so or by asking here, for example \"Create a draft campaign called Q1 agency owners.\"\n3. Offer what Kenso can help with, one line per area with its example ask. Where an ask says <campaign name>, use a real campaign from step 2, or leave that ask out when there is none.\n   - **Campaigns and replies**: \"Why did replies drop on <campaign name>, and what should I change?\"\n   - **Workspace setup**: \"Please set up my workspace.\"\n   - **Domains and inboxes**: \"Help me set up the inboxes I send from.\"\n   - **Deliverability**: \"Bounces are up. Are my domains and inboxes healthy?\"\n   - **Accounts and pipeline**: \"Which deals in my pipeline are stuck, and what is the next step on each?\"\n   - **Meetings**: \"Prep me for my next sales meeting.\"\n   - **Studio**: \"Help me plan a Studio page for my target accounts.\"\n   - **Workflows**: \"Help me plan a workflow that qualifies each new lead and flags the good ones.\"\n4. Only when step 2 listed a campaign, also offer a quick look at one of them, with its real name in the ask: \"Show me the leads in <campaign name>.\" or \"Show me the email sequence for <campaign name>.\"\n5. When the user picks an area, follow the Kenso skill for that job. If its text is not already in the conversation, `load_ken_skill` returns it by name.\n\nSome steps happen only in the Kenso app, such as connecting a mailbox, building a Studio template or a workflow, and changing a deal. The skill for that job links the page in the Kenso app (https://app.ken.so) where the user takes that step. Say so plainly; never claim a step was done here when the user has to do it in the app.\n\n## Rules\n\n- Work only in the workspace the user picked. Use only ids `list_workspaces` returned; do not guess workspace or client IDs. When the user names another of their workspaces, switch workspace_id to it.\n- Ask the user to confirm before any action that sends email, starts or resumes a campaign, or deletes data. Drafts, reads and blocklist additions do not need extra confirmation.\n- Kenso is for outreach to people in their business roles. Honor opt-outs: when someone asks not to be contacted, add them to the blocklist with `add_blocklist_entry`.\n- Kenso does not change plans, buy credits or process payments from the chat. Billing is managed by a workspace admin in the Kenso app.\n- Report tool errors in plain words and suggest the next step. Do not retry a failed write more than once.\n"
}

SHA-256 of public snapshot: 66253c09ef705cad3c76bfa31880c08612eadba1191843b005380f2e51ea7d20