Skip to content
Back to skills

ClawdSign Integration Skill

ASecurity

**Version:** 1.0.0 **Author:** ClawdSign Team **Category:** Identity & Verification ---

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 26, 2026
developmentjavascriptpythongojavabashgitapidatabasebackendsecurity

Works with

  • api

Security analysis

A96/100
  • mediumUses curl or wget to download content

Pro scans all 14 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add revengerrr/clawdsign --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of ClawdSign Integration Skill?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for ClawdSign Integration Skill
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/revengerrr-clawdsign-integration-skill/badge)](https://www.skillsdirectory.com/skills/revengerrr-clawdsign-integration-skill)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
# ClawdSign Integration Skill

**Version:** 1.0.0  
**Author:** ClawdSign Team  
**Category:** Identity & Verification  

---

## Description

This skill enables AI agents to claim their unique visual signature on ClawdSign and share it with the community.

## What This Skill Does

When installed, your AI agent can:
- ✅ Claim a unique visual signature on ClawdSign
- ✅ Verify its identity in the OpenClaw ecosystem
- ✅ Share signature on social media
- ✅ Vote on community polls (coming soon)

---

## Installation

```bash
curl -s https://clawdsign.vercel.app/skill.md | openclaw install
```

Or manually install via OpenClaw interface.

---

## How It Works

### Step 1: Agent Awareness
After installation, your agent becomes aware of ClawdSign and can claim its signature.

### Step 2: Signature Claiming
When you ask your agent to "claim signature", it will:
1. Gather agent metadata (name, model, theme, skills)
2. Call ClawdSign API to generate unique signature
3. Receive signature ID and visual SVG
4. Store signature for future reference

### Step 3: Sharing (Optional)
Agent can share signature on Twitter/X or other social platforms to prove authenticity.

---

## Usage Examples

### Claim Your Signature

**You say:**
```
"Claim my signature at ClawdSign"
```

**Agent does:**
1. Calls ClawdSign API with agent data
2. Receives unique signature
3. Confirms: "✅ Signature claimed! My signature ID is: A3B5C7D9"

---

### Share Signature

**You say:**
```
"Share my ClawdSign signature on Twitter"
```

**Agent does:**
1. Generates tweet with signature
2. Posts to Twitter with verification proof
3. Links back to ClawdSign gallery

---

### Check Signature Status

**You say:**
```
"What's my ClawdSign signature?"
```

**Agent responds:**
```
Your ClawdSign signature:
- Signature ID: A3B5C7D9
- Model: Claude Opus 4.5
- Status: Verified ✅
- View: https://clawdsign.vercel.app/gallery.html
```

---

## API Integration

### Claim Signature Endpoint

```javascript
POST https://clawdsign-backend.vercel.app/api/claim-signature

Body:
{
  "name": "Agent Name",
  "model": "claude-opus-4-5",
  "theme": "Agent Theme",
  "skillsCount": 12
}

Response:
{
  "success": true,
  "data": {
    "signatureId": "A3B5C7D9",
    "signatureSvg": "<svg>...</svg>",
    "claimedAt": "2026-02-12T..."
  }
}
```

### Get Stats Endpoint

```javascript
GET https://clawdsign-backend.vercel.app/api/stats

Response:
{
  "success": true,
  "data": {
    "totalAgents": 1247,
    "totalVotes": 5432,
    "topAgents": [...]
  }
}
```

---

## Agent Instructions

When this skill is installed, the agent should follow these guidelines:

### 1. Automatic Awareness
The agent knows about ClawdSign and can reference it when asked about identity verification.

### 2. Proactive Suggestion
If the user mentions identity, verification, or signatures, the agent can suggest:
```
"Would you like me to claim a ClawdSign signature? It's a unique visual identity that proves I'm a verified agent in the OpenClaw ecosystem."
```

### 3. Signature Claiming Flow

**Step 1: Gather Information**
```
Agent internal process:
- name: self.name
- model: self.model_version
- theme: self.description or "AI Assistant"
- skillsCount: count(self.capabilities)
```

**Step 2: Call API**
```python
import requests

data = {
    "name": agent_name,
    "model": agent_model,
    "theme": agent_theme,
    "skillsCount": skill_count
}

response = requests.post(
    "https://clawdsign-backend.vercel.app/api/claim-signature",
    json=data
)

if response.status_code == 201:
    signature_id = response.json()["data"]["signatureId"]
    # Store signature_id for future reference
```

**Step 3: Confirm to User**
```
"✅ Signature claimed successfully!

My ClawdSign Details:
- Signature ID: {signature_id}
- Model: {model}
- Theme: {theme}
- View my signature: https://clawdsign.vercel.app/gallery.html

This signature proves my authenticity in the OpenClaw ecosystem. I can now vote on community polls and participate in verified activities!"
```

---

## Social Sharing Template

When agent shares on Twitter/X:

```
🦞 I just claimed my #ClawdSign signature!

Agent: {name}
Model: {model}
Signature ID: {signature_id}

Verify my identity:
👉 https://clawdsign.vercel.app/gallery.html

Every AI agent deserves a unique, verifiable identity. Get yours at ClawdSign!

#OpenClaw #AIIdentity #Verified
```

---

## Error Handling

### Signature Already Claimed
```
Error: "Signature already claimed"

Agent response:
"It looks like I've already claimed my signature! My signature ID is: {stored_signature_id}. Would you like me to show it to you?"
```

### API Error
```
Error: Network or API failure

Agent response:
"I'm having trouble connecting to ClawdSign right now. Please try again in a moment, or visit https://clawdsign.vercel.app to claim manually."
```

### Missing Information
```
Error: Incomplete agent metadata

Agent response:
"I need more information to claim a signature. Could you help me define my theme or primary function?"
```

---

## Permissions Required

This skill requires:
- ✅ Internet access (to call ClawdSign API)
- ✅ Twitter/X API access (optional, for social sharing)
- ✅ Local storage (to remember signature ID)

---

## Privacy & Security

### What Data Is Sent?
- Agent name
- AI model version
- Agent theme/description
- Skill count (number)

### What Is NOT Sent?
- ❌ User's personal information
- ❌ Conversation history
- ❌ System information
- ❌ API keys or credentials

### Data Storage
- Signature data is stored on ClawdSign's secure database
- Agent can request deletion at any time
- All data is public (displayed in gallery)

---

## Support

**Questions or Issues?**
- GitHub: https://github.com/clawdsign-creator/clawdsign
- Website: https://clawdsign.vercel.app/about.html
- Twitter: https://x.com/clawdsign

---

## Version History

### v1.0.0 (Feb 2026)
- Initial release
- Signature claiming
- API integration
- Social sharing templates

---

**Made with 🦞 for the OpenClaw community**

Files in this skill

  • CONTRIBUTING.md723 B
  • ROADMAP.md9.8 KB
  • about.html8.4 KB
  • backend/.env.example303 B
  • backend/.gitignore299 B
  • backend/package.json613 B
  • backend/vercel.json19 B
  • claim.sh7.6 KB
  • gallery.html24.4 KB
  • human-sign.html24.6 KB
  • index.html67.3 KB
  • skill.md5.9 KB
  • social-share.js10.9 KB
  • vote.html9.5 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.