← Search

Generate Apify Actor output schemas from source code
Developer tools 🧪 Install ran in our test sandbox · Nov 18, 2026 📌 Pinned version: commit d522584
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: an Apify Actor codebase the agent can read and…

Generate Apify Actor output schemas from source code

Analyze an Actor's source to produce dataset_schema.json, output_schema.json and key_value_store_schema.json with Apify's hard rules (all-nullable, additionalProperties, empty required)

At a glance
What
Analyze an Actor's source to produce dataset_schema.json, output_schema.json and key_value_store_schema.json with Apify's hard rules (all-nullable, additionalProperties, empty required)
Cost
Free
Needs
an Apify Actor codebase the agent can read and analyze — the skill is a workflow the agent follows, not software
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Generate Apify Actor output schemas from source code is a free skill for Muse. Selected by Skill Harbor — short listing (the repo states no license, so no content is reproduced): @apify's skill for generating Actor output schemas — the files that tell Apify Console how to display run results.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit d522584

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: an Apify Actor codebase the agent can read and analyze — the skill is a workflow the agent follows, not software Install "Generate Apify Actor output schemas from source code" for me. It gives my agent @apify's 7-phase workflow for generating Actor output schemas: discover the Actor structure (find pushData/setValue calls, reuse existing TypeScript interfaces or Python TypedDicts, match repo conventions), generate dataset_schema.json (all output fields, every field nullable: true, additionalProperties: true and required: [] at both levels, anonymized examples), generate key_value_store_schema.json (collections by key or keyPrefix), generate the minimal output_schema.json, wire everything into actor.json, review against the checklist, and summarize. IMPORTANT: the repo states no license — fetch from the link only, and reproduce nothing beyond the link. Repository: https://raw.githubusercontent.com/apify/agent-skills/d522584df6d01746d76b0c674f375cc7d48a838f/skills/apify-generate-output-schema/SKILL.md Pinned version: install the code at commit d522584df6d01746d76b0c674f375cc7d48a838f exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "apify-generate-output-schema". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the Actor codebase and its .actor/ directory; nothing else — it's a workflow). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit d522584 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 18, 2026
👁 Observed during the install test · Nov 18, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
d522584 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 18, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.