Claude Skill

_template

Imported from apify/awesome-skills/skills/_template.

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Download apify-awesome-skills-skills__template-851fdfd.zip · 3 KB

Install

skills CLI npx skills add https://github.com/apify/awesome-skills/tree/main/skills/_template
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install apify-awesome-skills@llmmart
Git git clone https://github.com/apify/awesome-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole apify/awesome-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

REPLACE: Skill Title

REPLACE: One-line summary of what this skill helps the agent accomplish.

Example prompts

Prompts this skill handles:

  • "REPLACE: a real prompt a user would type"
  • "REPLACE: a second one, phrased differently"

Out of scope (the boundary):

  • "REPLACE: a nearby request this skill deliberately does not handle — and where to send it instead"

Prerequisites

Workflow

  1. REPLACE: Understand the user's goal, pick the right Actor(s).
  2. REPLACE: Fetch the Actor's input schema, build a valid input.
  3. REPLACE: Run the Actor, confirm with user if estimated cost is significant.
  4. REPLACE: Deliver results (count, format, link to dataset/console).

For a worked 4-step workflow, see apify/agent-skills ultimate-scraper.

Actor routing

User need Actor ID Tier Best for
REPLACE apify/REPLACE-actor apify REPLACE
REPLACE community/REPLACE-actor community REPLACE

Tier = apify (Apify-maintained, prefer) or community (third-party).

Calling Actors — choose your interface

Skills in this repo can call Actors via any of these interfaces. Pick the one that fits your runtime; cross-tool compatibility is your responsibility.

Option A: Apify CLI (recommended for portability)

Works in any shell-capable agent. Three flags on every call:

apify actors call "ACTOR_ID" -i 'JSON_INPUT' \
  --json \
  --user-agent apify-awesome-skills/REPLACE-skill-name \
  2>/dev/null
Flag Why
--json Stable machine-readable output
--user-agent Apify telemetry attribution
2>/dev/null Suppress progress messages that break JSON

Other useful commands:

# Search Actors
apify actors search "KEYWORDS" --json --limit 10 \
  --user-agent apify-awesome-skills/REPLACE-skill-name 2>/dev/null

# Fetch Actor schema
apify actors info "ACTOR_ID" --input --json \
  --user-agent apify-awesome-skills/REPLACE-skill-name 2>/dev/null

# Fetch results
apify datasets get-items DATASET_ID --format json \
  --user-agent apify-awesome-skills/REPLACE-skill-name 2>/dev/null

For the canonical command set with all flags, see apify/agent-skills ultimate-scraper.

Option B: Apify MCP connector

Hosted MCP server at https://mcp.apify.com. Documented at https://docs.apify.com/platform/integrations/mcp.

Option C: MCP client of your choice (e.g. mcpc)

Standalone CLI client. See https://github.com/apify/mcpc.

Troubleshooting

  • REPLACE: common error 1 → fix
  • REPLACE: common error 2 → fix
  • For detailed cost guardrails and recovery, see references/gotchas.md.
Files (awesome-skills)
  • references
    • actor-index.md 899 B
      Loading…
    • gotchas.md 1.3 KB
      Loading…
  • SKILL.md 3.4 KB
    ---
    # TEMPLATE — replace name and description with your real values.
    # Do NOT add real values here; this file is a starting point, not an installable skill.
    name: ""
    description: ""
    # metadata.keywords is required — comma-separated search terms for the catalog.
    metadata:
      category: data-extraction
      keywords: ""
    ---
    
    # REPLACE: Skill Title
    
    REPLACE: One-line summary of what this skill helps the agent accomplish.
    
    ## Example prompts
    
    Prompts this skill handles:
    
    - "REPLACE: a real prompt a user would type"
    - "REPLACE: a second one, phrased differently"
    
    Out of scope (the boundary):
    
    - "REPLACE: a nearby request this skill deliberately does not handle — and where to send it instead"
    
    ## Prerequisites
    
    - Apify account ([sign up](https://apify.com))
    - Authentication via one of:
      - `apify login` (OAuth, if using the Apify CLI)
      - `APIFY_TOKEN` environment variable
      - Token from [Apify Console → Settings → Integrations](https://console.apify.com/settings/integrations)
    
    ## Workflow
    
    1. REPLACE: Understand the user's goal, pick the right Actor(s).
    2. REPLACE: Fetch the Actor's input schema, build a valid input.
    3. REPLACE: Run the Actor, confirm with user if estimated cost is significant.
    4. REPLACE: Deliver results (count, format, link to dataset/console).
    
    For a worked 4-step workflow, see [apify/agent-skills ultimate-scraper](https://github.com/apify/agent-skills/blob/main/skills/apify-ultimate-scraper/SKILL.md).
    
    ## Actor routing
    
    | User need | Actor ID | Tier | Best for |
    |-----------|----------|------|----------|
    | REPLACE | `apify/REPLACE-actor` | apify | REPLACE |
    | REPLACE | `community/REPLACE-actor` | community | REPLACE |
    
    `Tier` = `apify` (Apify-maintained, prefer) or `community` (third-party).
    
    ## Calling Actors — choose your interface
    
    Skills in this repo can call Actors via any of these interfaces. Pick the one
    that fits your runtime; cross-tool compatibility is your responsibility.
    
    ### Option A: Apify CLI (recommended for portability)
    
    Works in any shell-capable agent. Three flags on every call:
    
        apify actors call "ACTOR_ID" -i 'JSON_INPUT' \
          --json \
          --user-agent apify-awesome-skills/REPLACE-skill-name \
          2>/dev/null
    
    | Flag | Why |
    |------|-----|
    | `--json` | Stable machine-readable output |
    | `--user-agent` | Apify telemetry attribution |
    | `2>/dev/null` | Suppress progress messages that break JSON |
    
    Other useful commands:
    
        # Search Actors
        apify actors search "KEYWORDS" --json --limit 10 \
          --user-agent apify-awesome-skills/REPLACE-skill-name 2>/dev/null
    
        # Fetch Actor schema
        apify actors info "ACTOR_ID" --input --json \
          --user-agent apify-awesome-skills/REPLACE-skill-name 2>/dev/null
    
        # Fetch results
        apify datasets get-items DATASET_ID --format json \
          --user-agent apify-awesome-skills/REPLACE-skill-name 2>/dev/null
    
    For the canonical command set with all flags, see [apify/agent-skills ultimate-scraper](https://github.com/apify/agent-skills/blob/main/skills/apify-ultimate-scraper/SKILL.md).
    
    ### Option B: Apify MCP connector
    
    Hosted MCP server at <https://mcp.apify.com>. Documented at
    <https://docs.apify.com/platform/integrations/mcp>.
    
    ### Option C: MCP client of your choice (e.g. `mcpc`)
    
    Standalone CLI client. See <https://github.com/apify/mcpc>.
    
    ## Troubleshooting
    
    - REPLACE: common error 1 → fix
    - REPLACE: common error 2 → fix
    - For detailed cost guardrails and recovery, see [references/gotchas.md](references/gotchas.md).
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.