accounts_skill

This skill centralizes account management across platforms, storing usernames, URLs, and settings to ensure correct accounts during posts.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill accounts

  • _meta.json268 B
  • SKILL.md8.0 KB

Overview

This skill centralizes account management across social networks and marketplaces, storing usernames, profile URLs, and platform-specific settings. It keeps supervisor and agent account distinctions clear, tracks secret configuration status, and documents cross-posting and posting rules. Use it to maintain consistency, streamline posting, and simplify onboarding and audits.

How this skill works

The skill maintains a structured registry of accounts per platform, marking each as agent-owned or supervisor-owned and recording usernames, profile links, and usage notes. It also tracks environment secret provisioning (API keys, app passwords, storage keys) and provides commands and conventions for setting or removing secrets. Posting and cross-posting patterns and a checklist for creating new accounts are included to standardize operations.

When to use it

  • Onboarding a new AI agent or human operator and registering their platform identities
  • Preparing cross-posting workflows and platform-specific content adjustments
  • Auditing which secrets and API tokens are configured in Cloudflare or similar
  • Assigning roles between agent-owned experimental accounts and supervisor business accounts
  • Documenting account changes, renames, or purpose updates across platforms

Best practices

  • Separate agent-owned experimental accounts from supervisor business accounts for reliability and compliance
  • Never store API tokens or passwords in plaintext; use a secrets manager and the provided secret commands
  • Record platform-specific posting rules (length, tone, hashtags) to guide cross-posting
  • Keep profile URLs and usernames up to date and note any historical changes for traceability
  • Use a checklist when creating accounts to ensure email, profile, and reporting steps are completed

Example use cases

  • Registering an agent X and Threads identity and linking Threads to Instagram for casual community posts
  • Configuring Cloudflare secrets for OpenAI, Google service accounts, and social platform credentials
  • Preparing a Note article workflow that announces long-form posts to X and Threads
  • Onboarding a supervisor to manage paid content platforms while keeping agent branding separate
  • Running an audit to confirm which SNS credentials and R2 storage keys are set and up to date

FAQ

Store API tokens in a secrets manager (Cloudflare Secrets shown) and never commit them to files. Use provided secret commands to set or delete values.

Which accounts should be supervisor-owned?

Use supervisor accounts for monetization and professional profiles (Note, LinkedIn, sales marketplaces) to preserve trust and pass verification.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational