coop-publishing

Save EDSL objects locally and publish them to Coop servers.

Updated Jun 4, 2025
One-click install
npx skills add https://github.com/expectedparrot/vernon --skill coop-publishing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coop-publishing
Source: https://github.com/expectedparrot/vernon/tree/main/macaw/ep-agent/skills/coop-publishing
Command: npx skills add https://github.com/expectedparrot/vernon --skill coop-publishing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill allows users to save EDSL objects locally and publish them to Coop, Expected Parrot's servers, for sharing.

Core Features & Use Cases

  • Local Persistence: Save EDSL objects to your local machine using obj.save('filename').
  • Coop Publishing: Push objects to Coop with configurable visibility (public, private, unlisted) and custom descriptions and aliases.
  • Use Case: A researcher can save their study agent list locally and then publish it as an unlisted item to Coop for collaboration.

Quick Start

Push the 'survey' object to Coop with unlisted visibility, a descriptive name, and a generated alias.

Frequently Asked Questions about coop-publishing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save EDSL objects to Coop for sharing?

To save and share EDSL objects, you can publish them to Coop servers using configurable visibility settings like public, private, or unlisted. This handles object persistence and allows controlled access for collaboration.

Can I save EDSL objects locally before publishing to a remote server?

Yes, you can save EDSL objects locally to your machine using the save function. This allows you to store your work locally before deciding to push and publish the objects to Coop servers for sharing.

What visibility settings are available when publishing EDSL objects to Coop?

When publishing EDSL objects to Coop, you can configure visibility settings to manage access. The available options are public, private, and unlisted, allowing you to control who can view or interact with your shared objects.

How do I generate an alias for an EDSL object published to Coop?

Generating an alias for an EDSL object published to Coop requires a user-provided descriptive name. The system uses this descriptive name to automatically generate an alias for the object during the publishing process.

What is the best way to collaborate on EDSL objects with other researchers?

The best way to collaborate on EDSL objects is by publishing them to Coop as unlisted items. This workflow allows you to save your study objects locally and then push them to Coop servers with custom descriptions for shared access.

Do I need a custom description to push an EDSL object to Coop servers?

Yes, providing a custom description is required when pushing an EDSL object to Coop servers. This description is necessary for alias generation and helps manage access through the controlled API during the publishing process.