3 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
What it does
- MANDATORY recipe for every Caffeine build that posts to X (Twitter) from a canister.
- The supported path is the `x-client` mops package (X API v2) over outbound HTTPS, with per-user OAuth 2.0 (PKCE, no client secret).
- Hand-rolling `ic.http_request` calls to `api.x.com` is a FORBIDDEN anti-pattern : it bypasses bearer auth, the non-replicated-outcall safeguard, and the package's null-field JSON handling.
- Load this skill whenever the user, spec, or any prior task mentions posting a tweet, "tweet this", X/Twitter, sharing to X, or any equivalent phrasing : and BEFORE writing any code that touches an X endpoint.
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads Connector X.
3 static scans, 0 counted findings.
Security state at 2026-09-30: reviewed. Static scans check the code, not how well the skill works.
State definitionsSelect the Files tab to load SKILL.md.
Skill details
Security scansReviewed
3 static scans, 0 counted findings. Security state at 2026-09-30: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.1. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: .
Cisco skill-scanner (Edge-run): cisco-skill-scanner/2.1.0. Scope: Local static, YARA, pipeline and behavioral analyzers; no LLM or AI Defense analysis. Raw findings: 1.
Semgrep Edge rules (Edge-run): semgrep/1.178.0+edge-rules.c15016a36fd3+offline-v1. Scope: Six Edge-authored static rules with Semgrep CE; offline execution and metrics disabled. Semgrep-maintained rules excluded. Raw findings: .
- Edge static checks
- Pass · 0 counted findings · 2026-09-27
- Cisco skill-scanner
- Pass · 0 counted findings · 2026-09-27
- Semgrep Edge rules
- Pass · 0 counted findings · 2026-09-27
Creator, source & licencecaffeinelabs
From the caffeinelabs public repository. Edge did not write or edit this skill.
- Repository
- caffeinelabs/skills
- Skill file
- View source at revision
- Revision
- e5cacdfe5ce55e939edb02980fca800c0c13f421
- Package hash
- sha256:e75e15e020d46c5242ab8accb9e116f87822cc4432ed2479d9113d613eca0781
- Licence
- Apache-2.0
- Description
- MANDATORY recipe for every Caffeine build that posts to X (Twitter) from a canister. The supported path is the `x-client` mops package (X API v2) over outbound HTTPS, with per-user OAuth 2.0 (PKCE, no client secret). Hand-rolling `ic.http_request` calls to `api.x.com` is a FORBIDDEN anti-pattern : it bypasses bearer auth, the non-replicated-outcall safeguard, and the package's null-field JSON handling. Load this skill whenever the user, spec, or any prior task mentions posting a tweet, "tweet this", X/Twitter, sharing to X, or any equivalent phrasing : and BEFORE writing any code that touches an X endpoint.
Quoted from the skill’s own description
Read skill files1 file
1 file, 6.2 KB at revision e5cacdfe5ce5.
Questions about Connector X
What does Connector X do?
MANDATORY recipe for every Caffeine build. Published by caffeinelabs (caffeinelabs/skills).
Is Connector X safe to use?
Edge security state: Reviewed (3 Edge-run static scans, scanned Sep 30, 2026). The Evidence tab shows the scan.
How do I use Connector X in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.
