Index of every page on this site: llms.txt
All skills
apify avatar

/apify-generate-output-schema

@410c3bf official
by apifyapify/agent-skills2.5k stars
281
Run it yourself

Deprecated. Output schema generation moved to the apify-actor-development skill; prefer that skill whenever it is available.

Use this Skill: https://skilld.dev/gh/apify/agent-skills/apify-generate-output-schema

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈39 tokens for metadata: the name and description. ≈255 when used: this file.

Description uses 1.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈155 characters, or 1.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Deprecated: use apify-actor-development

This skill is deprecated and will be removed in a future release. Generating and updating Actor output schemas (dataset_schema.json, output_schema.json, key_value_store_schema.json) is now part of the apify-actor-development skill.

  • If the apify-actor-development skill is available, load it and follow its references/output-schemas.md.
  • If it is not available, tell the user this skill is deprecated and help them install apify-actor-development from https://github.com/apify/agent-skills, then stop. Do not write the schemas from memory. Use the install method that fits their agent, preferably the same one this skill was installed with:
    • Claude Code plugin: /plugin install apify-actor-development@apify-agent-skills
    • Skills CLI, which works with most agents: npx skills add https://github.com/apify/agent-skills --skill apify-actor-development
    • Cloned repo: pull the latest changes; the skill is at skills/apify-actor-development/SKILL.md

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1mo4 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill is a developer tool designed to automate the generation of Apify Actor output schemas by analyzing local source code. It follows standard development practices, performing local file operations to create and update JSON configuration files without exhibiting malicious patterns or risky behaviors.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 410c3bf. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
metadata
{
  "deprecated": "true"
}

README badge

README badge for apify/agent-skills/apify-generate-output-schema

Generates JSON schema files for Apify Actors by analyzing their source code to define dataset, output, and key-value store structure. Use this when creating or updating Actor output schemas to ensure Apify Console displays run results correctly.

Generated from the current SKILL.md.

Does this skill work with Python Actors?
Yes. The skill searches for both JavaScript/TypeScript (`Actor.pushData()`, `Actor.setValue()`) and Python (`Actor.push_data()`, `Actor.set_value()`) calls, and can derive schemas from Python TypedDict, dataclass, or Pydantic model definitions.
Will this skill generate all three schema files?
It generates `dataset_schema.json` and `output_schema.json` for all Actors. `key_value_store_schema.json` is only generated if the Actor code contains `setValue` or `set_value` calls beyond the default INPUT key.
What if the Actor already has TypeScript type definitions for its output?
The skill reuses existing type definitions directly instead of recreating them from scratch — it derives schema fields from the type interface or class definition as the canonical source of truth.
Does this skill match existing repository conventions?
Yes. The skill searches for other Actor schemas in the repository during Phase 1 and matches their description style, field naming conventions, example formatting, view structure, and JSON formatting.
Will this skill use real user data in schema examples?
No. The skill anonymizes all example values — no real user IDs, usernames, or personal data appear in the generated schemas.

Generated from the current SKILL.md. These answers refresh after source changes.