guardian-verify-setup

Verify user identities for phone, Telegram, or Slack channels via CLI flows.

2|2|Updated May 13, 2026
One-click install
npx skills add https://github.com/autonomy-cloud/kairos-interface --skill guardian-verify-setup-autonomy-cloud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: guardian-verify-setup
Source: https://github.com/autonomy-cloud/kairos-interface/tree/main/skills/guardian-verify-setup
Command: npx skills add https://github.com/autonomy-cloud/kairos-interface --skill guardian-verify-setup-autonomy-cloud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of enabling secure, verified delivery of messages by connecting a user’s identity to a specific communication channel (phone, Telegram, or Slack) through an outbound verification flow.

Core Features & Use Cases

  • Channel selection & destination collection: Guides the user to choose the channel and provide the correct destination format (E.164 phone number, Telegram chat ID or handle, or Slack member ID).
  • Outbound verification session control: Creates, resends, cancels, and revokes verification sessions using the assistant CLI.
  • Proactive auto-checking: Polls for completion for voice (phone) and Slack to confirm verification without requiring the user to ask.

Quick Start

Ask the assistant to verify your identity on Slack, phone, or Telegram and follow the prompts to provide your destination and verification code.

Frequently Asked Questions about guardian-verify-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify my identity on phone, Telegram, or Slack for secure message delivery?

You can verify your identity on phone, Telegram, or Slack by selecting a channel, providing the correct destination format like an E.164 phone number or chat ID, and completing a code challenge to establish secure outbound delivery.

What formats do I need for phone, Telegram, and Slack channel verification?

Phone verification requires an E.164 phone number, Telegram requires a chat ID or handle, and Slack requires a member ID to correctly route the outbound verification session and validate the destination.

How do I manage outbound verification sessions using CLI automation?

You can manage outbound verification sessions via CLI automation by creating, resending, canceling, or revoking sessions to control the identity binding process and ensure secure message delivery.

Do I need to manually check if my Slack or voice phone verification is complete?

No, you do not need to manually check Slack or voice phone verification because the system proactively polls for completion using auto-checking to confirm verification without requiring you to ask.

Can I resend or cancel a verification code if I made a mistake during onboarding?

Yes, you can resend or cancel a verification code during onboarding by invoking the respective CLI flows, allowing you to correct destination identifiers or abort the outbound session safely.