Operate the anysite command-line tool for web data extraction, batch API processing, multi-source dataset pipelines with scheduling/transforms/exports, database operations, and LLM-powered data analysis. Use when users ask to collect data from LinkedIn, Instagram, Twitter, or any web source via CLI; create or run dataset pipelines; schedule automated collection; batch-process API calls; query collected data with SQL; load data into PostgreSQL or SQLite; analyze data with LLM (summarize, classify, enrich, match, deduplicate); or work with anysite commands. Triggers on anysite CLI usage, data collection, dataset creation, scraping, API batch calls, scheduling, database loading, or LLM analysis tasks.
Command-line tool operator for anysite CLI. Execute web data extraction, batch API processing, multi-source dataset pipelines, and database operations through Claude.
Developer: Anysite Skills Contributors
The Anysite CLI skill enables Claude to operate the anysite command-line tool for data collection and processing. Claude can execute anysite commands via Bash to collect data from LinkedIn, Instagram, Twitter/X, Y Combinator, and other web sources, create dataset pipelines, run SQL queries, and load data into PostgreSQL or SQLite databases.
This skill is designed for users who have the anysite CLI installed and want Claude to help orchestrate data collection workflows.
Anysite CLI must be installed:
pip install anysite-cli
Configure your API key:
anysite config set api_key sk-xxxxx
Or set environment variable:
export ANYSITE_API_KEY=sk-xxxxx
Update schema cache (required):
anysite schema update
See full installation guide: https://docs.anysite.io/cli
# Add the marketplace (if not already added)
/plugin marketplace add https://github.com/anysiteio/agent-skills
# Install the skill
/plugin install anysite-cli@anysite-skills
Once installed, Claude can execute anysite CLI commands to help with data collection tasks.
Single API call:
"Get LinkedIn profile for satyanadella"
→ Executes: anysite api /api/linkedin/user user=satyanadella --format table
Batch processing:
"Collect LinkedIn profiles for all users in users.txt, save as CSV"
→ Executes: anysite api /api/linkedin/user --from-file users.txt --input-key user --format csv --output profiles.csv --parallel 5 --stats
Endpoint discovery:
"Show me all LinkedIn API endpoints"
→ Executes: anysite describe --search "linkedin"
Dataset creation:
"Create a dataset to collect company info and their employees"
→ Creates dataset.yaml with sources and dependencies
→ Executes: anysite dataset collect dataset.yaml
Database loading:
"Load the collected dataset into PostgreSQL"
→ Executes: anysite dataset load-db dataset.yaml -c pg
Execute individual API calls with field selection and output formatting:
# Basic call
anysite api /api/linkedin/user user=satyanadella
# With formatting
anysite api /api/linkedin/company company=anthropic --format table
# Field selection
anysite api /api/linkedin/user user=satyanadella --fields "name,headline,follower_count"
# Save to file
anysite api /api/linkedin/search/users title=CTO count=50 --format csv --output ctos.csv
Process multiple inputs with parallel execution and rate limiting:
# From text file (one value per line)
anysite api /api/linkedin/user --from-file users.txt --input-key user --parallel 5
# With rate limiting and progress
anysite api /api/linkedin/user --from-file users.txt --input-key user \
--rate-limit "10/s" --on-error skip --progress --stats
# Pipe from stdin
cat companies.txt | anysite api /api/linkedin/company --stdin --input-key company \
--format csv --output results.csv
Create multi-source datasets with dependencies, transforms, and exports:
Initialize:
anysite dataset init my-dataset
Configure dataset.yaml:
name: my-dataset
sources:
- id: companies
endpoint: /api/linkedin/company
from_file: companies.txt
input_key: company
transform:
filter: '.employee_count > 10'
fields: [name, url, employee_count]
export:
- type: file
path: ./output/companies-{{date}}.csv
format: csv
- id: employees
endpoint: /api/linkedin/company/employees
dependency:
from_source: companies
field: urn.value
input_key: companies
input_template:
companies:
- type: company
value: "{value}"
count: 5
storage:
format: parquet
path: ./data/
schedule:
cron: "0 9 * * *"
Collect and query:
# Preview plan
anysite dataset collect dataset.yaml --dry-run
# Run collection
anysite dataset collect dataset.yaml
# Collect and auto-load into database
anysite dataset collect dataset.yaml --load-db pg
# Query with SQL
anysite dataset query dataset.yaml --sql "SELECT * FROM companies LIMIT 10"
# Interactive SQL shell
anysite dataset query dataset.yaml --interactive
Manage database connections and load data:
# Add connection
anysite db add pg # Interactive prompts
# Test and inspect
anysite db test pg
anysite db schema pg --table users
# Insert data
cat data.jsonl | anysite db insert pg --table users --stdin --auto-create
# Query
anysite db query pg --sql "SELECT * FROM users" --format table
Universal API Access
api command for all endpointsBatch Processing
Dataset Pipelines
Database Integration
DuckDB Querying
User Request
↓
anysite-cli Skill (This)
↓
Bash Execution
↓
Anysite CLI Commands
↓
Anysite API / Local Database
Claude interprets your data collection needs and executes the appropriate anysite CLI commands via Bash. All commands use the anysite prefix and follow the patterns documented in the skill.
# Initialize dataset
anysite dataset init company-intel
# Edit dataset.yaml with sources, transforms, schedule...
# Then collect and load
anysite dataset collect company-intel/dataset.yaml --load-db pg
# Query results
anysite db query pg --sql "SELECT c.name, COUNT(e.id) FROM companies c JOIN employees e ON e.companies_id = c.id GROUP BY c.name" --format table
# Set up daily schedule
anysite dataset schedule company-intel/dataset.yaml --incremental --load-db pg
anysite api /api/linkedin/user --from-file people.txt --input-key user \
--parallel 5 --rate-limit "10/s" --on-error skip \
--fields "name,headline,location,follower_count" \
--format csv --output people.csv --stats
anysite describe --search "linkedin"
anysite describe /api/linkedin/company
anysite api /api/linkedin/company company=anthropic --format table
The skill includes comprehensive reference guides:
All API commands support multiple output formats:
--format json - Pretty JSON (default)--format jsonl - Newline-delimited JSON for streaming--format csv - CSV with headers--format table - Rich table for terminal displayThe anysite CLI provides access to 65+ API endpoints across platforms:
| Platform | Example Endpoints | |----------|-------------------| | LinkedIn | Users, companies, search, posts, comments, employees | | Instagram | Users, posts, comments, followers | | Twitter/X | Users, posts, search | | Reddit | Posts, comments, subreddits | | YouTube | Videos, channels, comments | | Y Combinator | Companies, founders, batches | | SEC | Company filings, documents | | Web | Page parsing, sitemap extraction |
Use anysite describe to discover all available endpoints.
The anysite CLI uses a config file at ~/.anysite/config.yaml.
Configuration priority:
--api-key)ANYSITE_API_KEY)~/.anysite/config.yaml)Manage config:
anysite config set api_key sk-xxxxx
anysite config get api_key
anysite config list
anysite config init
anysite-cli/
├── SKILL.md # Skill definition
├── README.md # This file
└── references/
├── api-reference.md # CLI command reference
└── dataset-guide.md # Pipeline and database guide
"anysite: command not found"
pip install anysite-clianysite --version"API key not configured"
anysite config set api_key sk-xxxxxexport ANYSITE_API_KEY=sk-xxxxx"Schema cache not found"
anysite schema update"Database connection failed"
anysite db test <name>~/.anysite/connections.yamlFound a bug or have a feature request? Submit an issue at: https://github.com/anysiteio/agent-skills/issues
MIT License - see LICENSE file for details
Note: This skill requires the anysite CLI to be installed and configured. Get your API key at anysite.io.
Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer