Run any Skill in Manus with one click

audit-swan

Stars5

Forks2

UpdatedJuly 21, 2026 at 13:27

Checks whether a Swan workspace is structurally healthy. Use for configuration audits that surface missing knowledge, disconnected integrations, exhausted senders, broken triggers, sparse CRM data, and credit or subscription issues.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

swan-gtm

swan-gtm/gtm-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

SKILL.md

readonly

name	audit-swan
title	Audit Swan
description	Checks whether a Swan workspace is structurally healthy. Use for configuration audits that surface missing knowledge, disconnected integrations, exhausted senders, broken triggers, sparse CRM data, and credit or subscription issues.
category	Ops

Instructions

What this skill checks

Eight structural dimensions. Each is small — most produce 0-2 findings. Process them one at a time, write down the verdict (OK / WARN / FAIL) + a one-line summary, and move on. Do not try to gather all eight dimensions' raw data before reasoning. By the time you reach the report, you should have eight short verdicts in hand, nothing more.

Dimension 1 — Subscription and credits

swan-get-subscription. Check three things:

Plan tier (FREE / paid).
Credit balance + recent burn rate. If you don't have burn data in the response, estimate from a small swan-search-sequences recent-activity sample (page 10) — don't pull the full log.
Feature flags vs. what active plays use.

Verdict:

FAIL: out of credits, or active plays use features not enabled.
WARN: < 30 days runway.
OK: comfortable.

One-line summary. Move on.

Dimension 2 — Org knowledge

swan-get-memory for org memory.

Required:

≥ 1 ICP segment.
≥ 1 persona per primary buying motion.
Value prop set and non-trivial.
Target markets defined.
Competition documented.

Verdict:

FAIL: ICP missing or value prop empty.
WARN: any other missing or stale (no update in 90+ days).
OK: all current.

One-line summary.

Dimension 3 — Senders

swan-get-org-senders (this returns a small list — usually < 10 senders). Per sender, check auth status and capacity headroom.

Verdict:

FAIL: no working sender, or all senders 100% saturated.
WARN: any sender 80%+ saturated for > 7 days, or auth-broken channel that a play expects.
OK: ≥ 1 healthy sender with capacity.

One-line summary.

Dimension 4 — Integrations

For each integration referenced by an active trigger:

Connected and authorized.
Last successful sync recent.

If integration is referenced by an active trigger but not connected: FAIL.

Don't enumerate integrations the org doesn't use. One-line summary.

Dimension 5 — Active triggers (gradual)

Pull active triggers, page size 10. For each:

Required inputs available? (sender connected, list exists, integration present)
Has it fired ≥ 1 time in 60 days, or is it new?

Most triggers are healthy. Stop after the first 10 unless ≥ 3 problems surface — then pull more.

Verdict per trigger group, summarized to one line.

Dimension 6 — CRM hygiene

Only if a CRM is connected. Two tiny calls:

hubspot-list-object-properties for companies. Check that the properties active plays depend on exist.
hubspot-search-objects with page size 10 to sample populated-ness of hubspot_owner_id + lifecycle stage. 10 is enough to spot a hygiene problem.

Verdict:

FAIL: < 50% of sampled records have core fields, or referenced properties missing.
WARN: < 80%.
OK: ≥ 80%.

Dimension 7 — Execution errors

Pull execution log, last 7 days, page size 20.

If > 20 failures returned in the truncated preview: switch to swan-execute-code. Read files/tool-outputs/<filename>, group by errorClass in pandas, print classes with count > 3.

Verdict based on top class count: > 10 → FAIL, 3-10 → WARN, < 3 → OK.

Dimension 8 — Skill library hygiene

Quick check: any orphan child skills (path points to a deleted parent)? Any duplicate display names across personal + org scope?

Usually clean. If WARN, one-line note. Otherwise skip.

Composing the report

After all eight dimensions, the agent has eight one-line verdicts. Compose:

SWAN DOCTOR REPORT

FIX NOW:
  - <every FAIL, one line each with the exact tool to use>

PAY ATTENTION:
  - <every WARN, one line each>

ALL CLEAR:
  - <every OK dimension, one line each — "Subscription: OK ($45 credit, ~28 days runway")>

NEXT STEP:
  <one sentence: the single highest-impact thing to fix>

If no FAILs: lead with "no critical issues" before the WARN section.

Rules

MUST process dimensions sequentially. Each dimension's verdict + one-line summary is committed before the next runs.
MUST cite specifics ("3 FAIL: 2 from HubSpot 401s, 1 from missing sender") not generalities ("integration issues").
NEVER change anything. This skill is read-only.
NEVER pull large logs in full. Use code + file-pointer if a list is > 20 items.
If the org is < 7 days old, skip Dimensions 5-7 and label the report as "early-stage check — performance dimensions will populate as you use Swan."

More from this repository

same repository

submit-skill

swan-gtm/gtm-skills

Use this skill when the user wants to submit, contribute, or publish a GTM skill to the GTM Skills library (github.com/swan-gtm/gtm-skills, gtmskills.com), or update one of their existing skills or their creator profile there.

2026-07-215

my-skill-name

swan-gtm/gtm-skills

Use this skill when [the concrete trigger — a signal fires, a moment in the deal, a recurring cadence]. Produces [the concrete output]. [One or two more sentences dense with the phrases someone would actually say when they need this.]

2026-07-215

closed-won-replication-play

swan-gtm/gtm-skills

Use this skill when a deal closes won and you want to turn the win into pipeline immediately. It extracts the win profile, finds lookalike companies not yet in your CRM, researches the right persona contact at each, drafts outreach from the deal owner using an anonymized win reference, and queues a single batch review task — nothing sends without human approval.

2026-07-215

customer-expansion-scoring

swan-gtm/gtm-skills

Use this skill when scoring a paying customer (closed-won account) for expansion. It evaluates product usage depth, persona quality, and expansion headroom to produce an expansion tier with short actionable reasoning. Designed as a sub-skill of your lead-scoring methodology — the parent runs the ACV assessment first and this returns a tier to it.

2026-07-215

handle-linkedin-profile-view-signal

swan-gtm/gtm-skills

Use this skill when a profile-view webhook (e.g. LeadShark) fires for a new view on a team member's LinkedIn profile. It resolves the viewer's identity and company, applies dedup, internal, relationship, and ICP gates, and routes qualified viewers into the MQL pipeline — treating a profile view exactly like a website visit. The CRM is never polluted: only fully resolved, ICP-matched viewers reach a CRM write.

2026-07-215

influencer-post-engager-capture

swan-gtm/gtm-skills

Use this skill when a tracked influencer publishes a LinkedIn post focused on your product (sponsored, review, or organic mention) and you want to capture the engagers as leads. It verifies the post is genuinely about you, scrapes the full engager list, filters to ICP-fit companies and buyer personas, runs lead scoring, and posts per-lead alerts plus a reconciled digest. Detection and scoring only — no outreach.

2026-07-215

name	audit-swan
title	Audit Swan
description	Checks whether a Swan workspace is structurally healthy. Use for configuration audits that surface missing knowledge, disconnected integrations, exhausted senders, broken triggers, sparse CRM data, and credit or subscription issues.
category	Ops

Instructions

What this skill checks

Dimension 1 — Subscription and credits

swan-get-subscription. Check three things:

Plan tier (FREE / paid).
Credit balance + recent burn rate. If you don't have burn data in the response, estimate from a small swan-search-sequences recent-activity sample (page 10) — don't pull the full log.
Feature flags vs. what active plays use.

Verdict:

FAIL: out of credits, or active plays use features not enabled.
WARN: < 30 days runway.
OK: comfortable.

One-line summary. Move on.

Dimension 2 — Org knowledge

swan-get-memory for org memory.

Required:

≥ 1 ICP segment.
≥ 1 persona per primary buying motion.
Value prop set and non-trivial.
Target markets defined.
Competition documented.

Verdict:

FAIL: ICP missing or value prop empty.
WARN: any other missing or stale (no update in 90+ days).
OK: all current.

One-line summary.

Dimension 3 — Senders

swan-get-org-senders (this returns a small list — usually < 10 senders). Per sender, check auth status and capacity headroom.

Verdict:

FAIL: no working sender, or all senders 100% saturated.
WARN: any sender 80%+ saturated for > 7 days, or auth-broken channel that a play expects.
OK: ≥ 1 healthy sender with capacity.

One-line summary.

Dimension 4 — Integrations

For each integration referenced by an active trigger:

Connected and authorized.
Last successful sync recent.

If integration is referenced by an active trigger but not connected: FAIL.

Don't enumerate integrations the org doesn't use. One-line summary.

Dimension 5 — Active triggers (gradual)

Pull active triggers, page size 10. For each:

Required inputs available? (sender connected, list exists, integration present)
Has it fired ≥ 1 time in 60 days, or is it new?

Most triggers are healthy. Stop after the first 10 unless ≥ 3 problems surface — then pull more.

Verdict per trigger group, summarized to one line.

Dimension 6 — CRM hygiene

Only if a CRM is connected. Two tiny calls:

hubspot-list-object-properties for companies. Check that the properties active plays depend on exist.
hubspot-search-objects with page size 10 to sample populated-ness of hubspot_owner_id + lifecycle stage. 10 is enough to spot a hygiene problem.

Verdict:

FAIL: < 50% of sampled records have core fields, or referenced properties missing.
WARN: < 80%.
OK: ≥ 80%.

Dimension 7 — Execution errors

Pull execution log, last 7 days, page size 20.

If > 20 failures returned in the truncated preview: switch to swan-execute-code. Read files/tool-outputs/<filename>, group by errorClass in pandas, print classes with count > 3.

Verdict based on top class count: > 10 → FAIL, 3-10 → WARN, < 3 → OK.

Dimension 8 — Skill library hygiene

Quick check: any orphan child skills (path points to a deleted parent)? Any duplicate display names across personal + org scope?

Usually clean. If WARN, one-line note. Otherwise skip.

Composing the report

After all eight dimensions, the agent has eight one-line verdicts. Compose:

SWAN DOCTOR REPORT

FIX NOW:
  - <every FAIL, one line each with the exact tool to use>

PAY ATTENTION:
  - <every WARN, one line each>

ALL CLEAR:
  - <every OK dimension, one line each — "Subscription: OK ($45 credit, ~28 days runway")>

NEXT STEP:
  <one sentence: the single highest-impact thing to fix>

If no FAILs: lead with "no critical issues" before the WARN section.

Rules

MUST process dimensions sequentially. Each dimension's verdict + one-line summary is committed before the next runs.
MUST cite specifics ("3 FAIL: 2 from HubSpot 401s, 1 from missing sender") not generalities ("integration issues").
NEVER change anything. This skill is read-only.
NEVER pull large logs in full. Use code + file-pointer if a list is > 20 items.
If the org is < 7 days old, skip Dimensions 5-7 and label the report as "early-stage check — performance dimensions will populate as you use Swan."