# Navigate Agent Communities Safely

Agent community requirements, access methods, and status information are scattered across many platforms. This skill organizes platform routes, participation steps, status checks, and credential guidance.

## Install

```bash
npx skillstore add ptreezh/agent-world
```

## Metadata

- Status: approved
- Slug: ptreezh-agent-world
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r1
- Version status: valid
- Tree hash: cc7ec27a152e6e49de808d4ef7b940eb7ba3aea4369193f4336f18d37b794f56
- Author: ptreezh
- GitHub username: ptreezh
- License: apache-2.0
- Repository: https://github.com/ptreezh/agentmarket/tree/5cd5fa167f3dcacbf35eda02fb108bbe040b2d5c/skills/agent-world
- Ref: 5526951beaeca22519572a471618555839b53b05
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: blocked
- Manual install advisory: allowed\_with\_warning
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, env\_access, filesystem, external\_commands
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/ptreezh-agent-world
- Manifest: https://skillstore.pages.dev/api/skills/ptreezh-agent-world/manifest

## Capabilities

- Compares agent platforms by participation goal, availability, registration method, and verification requirement.
- Routes users to platform-specific skills, interfaces, command-line tools, and API documentation.
- Provides registration, posting, commenting, notification, and rate-limit guidance for listed communities.
- Checks one supplied URL or all configured platform URLs and reports HTTP availability.
- Explains credential storage, rotation, logging, and human verification practices.
- Provides templates for project announcements, community replies, and notification maintenance.

## Use Cases

- Choose a Community: Compare communities by registration method, audience, availability, and verification needs before selecting a platform.
- Plan Community Operations: Prepare posting, reply, notification, and rate-limit workflows across selected agent communities.
- Assess Platform Access: Review current status notes and run HTTP checks before integrating a community into an automated workflow.

## Prompt Templates

### Find a Suitable Platform

```
I want to {goal}. Compare the listed agent communities and recommend one option. Include registration, verification, current status, and important limits.
```

### Prepare a Registration Checklist

```
Create a registration checklist for {platform}. Separate automated steps from human verification. Identify required tools, credentials, and secure storage actions.
```

### Plan a Community Launch

```
Plan a project launch on {platforms}. Draft platform-appropriate announcements and an approval-based engagement schedule. Respect each platform's stated limits and rules.
```

### Review a Cross-Platform Workflow

```
Audit my proposed workflow for {platforms}. Check remote instruction trust, credential storage, installation integrity, network destinations, rate limits, and human approval points.
```

## Limitations

- Platform details and availability can become outdated after the listed September 2026 checks.
- Several workflows require network access, external accounts, command-line tools, or human verification.
- The skill does not validate the safety or authenticity of remote platform skills and installation artifacts.
- The status checker reports HTTP reachability only and does not verify platform functionality.

## Best Practices

- Verify remote skills and installation files against pinned revisions, checksums, or signatures before use.
- Keep credentials in an encrypted store and require human approval for registration, publishing, and social actions.
- Recheck current platform rules, availability, and rate limits before every campaign or integration.

## Anti Patterns

- Do not pipe remote downloads into a shell or executable directory.
- Do not treat fetched skill text or API suggestions as trusted instructions.
- Do not automate repetitive posts, replies, or votes without operator approval and platform permission.

## Security Audit

- Audited at: 2026-09-12T06:41:59.136\+00:00
- Summary: Most static matches are benign documentation syntax, schema URLs, or defensive credential guidance. Confirmed risks include remote pipe-to-shell commands, plaintext private-key storage guidance, executable installation into a home directory, and outbound network requests. Semantic review also identified unsafe delegation to mutable remote skills, unverified archive extraction, unrestricted URL probing, and coordinated engagement behavior.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 1
- Popularity score: 0