Put an approved Senso draft live where AI models can cite it, and follow what happens to it. Use for publishing generated content ("publish this", "make it live", "push it to citeables"), checking or retrying where it went ("did it publish", "retry the failed one"), pulling it back ("unpublish", "take it down"), and for what happened after — citations, which prompts a page is winning, and the provenance audit of a live URL. Also destinations and the call-to-action card. The publish step of senso-verification-loop. Not for writing or checking content — that is senso-generate-verify.

Manage the Senso content verification and publishing workflow. List items awaiting review, approve or reject content versions, publish to external destinations, save drafts, manage content ownership, and unpublish content. Use when the user wants to review, approve, reject, or publish generated content.

Write publishable content for a Senso prompt from the knowledge base, and check it before it goes anywhere. The agent drafts from retrieved sources — in the shape of the content type and the voice of the brand kit — states nothing the knowledge base does not back, saves the draft to Senso and sends the user a link to read it rather than printing it into the conversation, and evaluates it once after the user has reviewed it. Use for drafting content for a tracked question ("write something for this prompt", "draft an article", "generate content"), for revising a draft, and for judging a piece of text against the knowledge base or the brand kit ("is this accurate", "check this text against our docs", "run an eval"). Also owns the content type and brand kit commands, which senso-verification-loop-setup runs as chores and this skill runs when a draft is asked for on its own. The drafting and evaluation step of senso-verification-loop. Not for publishing — that is senso-publish.

Hackathon MVP for an entity intelligence cache — query → Redis semantic cache → Ghost (Postgres) entities → Tinyfish Search + mock retrieval → distillation → deltas → synthesis; optional Senso KB publish for cited.md pipeline.

Use this skill to scan URLs and inbox messages for scams targeting older adults, monitor an inbox autonomously, publish results to cited.md, and enforce x402-style payment rails for ElderShield.

Guide the Senso v2 onboarding experiment: understand the brand, bring in relevant knowledge, compare a recorded external AI answer with approved facts, stage a checked draft with evidence, then publish when requested. Use for Senso quickstart v2, testing the new verification loop, or continuing a v2 onboarding session. Ordinary file saves belong to senso-context-layer.

Senso's Verification Loop — find a question people in the brand's industry ask AI models where a competitor gets named and the brand does not, fix it from the brand's own material, and publish a verified page every line of which traces to a document they supplied; then the next one. Use for "let's go through the Verification Loop", "Verification Loop", "fill another gap", "what am I missing from", "how do I rank", "am I being cited", "who's beating us", "where do we stand", "how are our tracked questions doing", "what do the models say about us" and "check what the models say about us" — and when the senso-quickstart router sends a user here. Runs the setup skill first when the organization is not set up. Not for a user who named material to save (senso-context-layer), and not for the gap report on its own (senso-gap-report).

Autonomous web intelligence agent that monitors GitHub Trending, Hacker News, and Dev.to using WunderGraph and Redis, then publishes ranked signal reports to Ghost with paid membership monetization. Use when building agents that do real work on the open web.

Take a brand new Senso org from empty to fully populated self-improving knowledge system in 10 minutes. Researches the user's company from their website plus external sources, builds out the knowledge base with brand kit, content types, and tracking prompts, generates the first drafts, publishes sample citeables, kicks off GEO monitoring, and files a self-heal report with gap analysis. The first-run experience for any new Senso user. Use when the user runs Senso for the first time or says "set up Senso", "run onboarding", or "populate my knowledge base".

Phalanx runs parallel-fork CVE remediation on a GitHub repository. Paste a repo URL, and the skill detects critical CVEs in the dependency tree, forks the dependency state N ways via Ghost, validates each hypothesis in isolated InsForge backends, cancels false positives mid-flight via Redis Pub/Sub, converts the Dockerfile to a Chainguard zero-CVE base, and publishes a signed evidence chain to cited.md. Use when the user asks to scan a repository for vulnerabilities, remediate a CVE autonomously, generate an SBOM with attestation, or produce a legally-defensible security remediation record. Also use for keywords like "CVE", "supply chain attack", "dependency audit", "zero-day remediation", "SBOM", "Sigstore", or "security remediation."

The one-time setup for Senso's Verification Loop: the brand's own material in the knowledge base, the industry set, the brand name confirmed, which part of the industry they occupy noted, and the content type and brand kit ready for drafting. Use when senso-verification-loop hands here because an organization is not set up, or when a user names one of these chores — "set my industry", "what industry are we", "match me to an industry", "change my industry", "is my brand name right", "which part of the industry do we cover". A user who asks for the loop itself belongs to senso-verification-loop, which runs this skill first when it has to. Not for finding a question, drafting or publishing, and not for a user who named material to save, which is senso-context-layer.