Publisher Factory

For Claude: How to Use This Skill

Use this skill when an operator asks to create or refresh Seren publishers for a company, a SaaS category, or a competitive set. The skill is review-and-build automation for publisher definitions: it verifies what exists, researches only official API surfaces, and deploys validated publishers using the live Asana publisher as the commercial template.

This skill follows the Seren SkillForge file layout. The executable runtime is the generic parameterized factory at scripts/agent.py. Do not add vendor-specific scripts such as run_calendly_probe.py; the same runner must handle any company, calendar app, SaaS API, competitor set, or adjacent category leader through inputs.

When to Use

• create a publisher for a company
• create publishers for a product category
• generate API integration publishers for competitors
• clone the Asana publisher pattern for another SaaS/API company
• build publishers for adjacent category leaders

Mandatory Live Catalog Guard

Before saying any third-party service is available or unavailable, call list_agent_publishers with no arguments. Do this on every run. The publisher catalog is live and changes frequently.

After the empty-argument catalog call:

1. Call list_agent_publishers with the target company search term and verbose: true to discover fuzzy matches.
2. Call get_agent_publisher with the normalized target slug for the exact existence check. A fuzzy search result is not an existing publisher unless its slug or display name exactly matches the target.
3. Call get_agent_publisher with slug: "asana" and use that live Asana publisher as the source template.
4. If a candidate publisher already exists, report it under existing unless the operator explicitly asked to update it.
5. Never rely on memory, stale local docs, or prior runs to decide publisher availability.

Required Inputs

Ask for missing inputs only when needed:

• target company or product category
• whether existing publishers may be updated
• preferred naming convention if the operator has one

Executable Commands

Run the generic factory probe with a target:

python3 scripts/agent.py --target "Calendly"

Run from config:

python3 scripts/agent.py --config config.json

The runtime emits the standard grouped report:

• deployed
• existing
• updated
• skipped
• blocked

The default mode is dry-run. Use the runtime to validate the live catalog, exact publisher lookup, Asana template load, organization resolution, and OAuth provider/user-token gates before creating or updating publishers.

Default discovery scope:

• include the target company
• include the top 10 competitors
• include adjacent category leaders until the run reaches 20 companies total

Research Workflow

For each candidate company:

1. Identify the official website and official public API docs.
2. Verify API availability, auth style, base URLs, endpoint families, and rate limits using the Perplexity Seren publisher.
3. Prefer official documentation over blog posts, SDK examples, generated snippets, and reverse-engineered browser traffic.
4. Skip the company if public API docs cannot be found or API access is unclear.
5. Record the skip reason in the inline report.

Do not create publishers from unofficial endpoints, hidden browser APIs, private partner APIs, invite-only APIs, or undocumented routes.

Publisher Template Rules

Clone the live Asana publisher exactly for commercial and ownership settings:

• pricing fields
• owner fields when exposed by the live publisher response
• x402 wallet address and wallet network/Base network settings
• contact and support metadata where applicable
• prepaid and onchain billing settings
• minimum balance and low-balance thresholds

Do not hard-code old Asana values. Read the live Asana publisher during the run and copy the relevant values into each new publisher.

Resolve the deployment organization explicitly. create_publisher requires organization_id, and publisher detail responses may not expose it. Call list_organizations and use the operator-selected organization, or the single personal organization when only one is returned. If multiple organizations are available and the operator has not selected one, ask before deployment.

Do not clone Asana product-specific fields:

• API URL
• endpoint catalog
• capability claims
• auth documentation
• OAuth provider ID or slug
• resource descriptions

Generated Publisher Contract

Every generated publisher must include:

integration_type: api
publisher_category: integration
billing_model: x402_per_request
default_response_format: json
undocumented_endpoint_policy: default_deny

Every generated publisher must also include:

• clear capability summaries
• usage examples
• resource descriptions
• auth documentation
• endpoint catalog
• protected destructive endpoints

Auth support:

• Use OAuth when the official API supports OAuth.
• Use API key auth when the official API uses token or key based access.
• If both OAuth and API key auth are supported, include both and mark the preferred official flow.
• For user-owned personal access tokens or bearer tokens, use a gateway supported user-token path such as passthrough headers or token exchange. Do not convert a user's PAT into a shared static upstream key.
• If OAuth is selected, first list the organization OAuth providers and reuse a target-specific provider only when it already exists for that company. Create a new target-specific provider only when the required client credentials and official OAuth URLs are available.
• Never reuse Asana's OAuth provider for another company.
• If the API is OAuth-only and no target-specific OAuth provider can be resolved or created, block deployment and report the missing OAuth provider as the next action.

Endpoint catalog rules:

• Include read, write, update, and delete endpoints when the official API documents them.
• Mark destructive endpoints such as delete, revoke, archive, cancel, remove, purge, or disable as protected.
• Default deny any endpoint not explicitly catalogued.

Logo rules:

• Use an official 200 x 200 logo when available.
• Missing official logo is non-blocking.
• Continue deployment with logo_status: missing when no compliant logo is available.

Deployment Gates

Deploy or update only after all required gates pass:

1. Live publisher catalog was queried with no arguments.
2. Existing publisher status was checked with get_agent_publisher.
3. The live Asana publisher was loaded with get_agent_publisher as the commercial template.
4. Deployment organization_id was resolved with list_organizations.
5. Official API docs were found.
6. Perplexity verification passed.
7. Authentication method is known.
8. OAuth provider or user-token path is valid when user auth is required.
9. Endpoint catalog is populated from official docs.
10. Destructive endpoints are marked protected.
11. Basic health check passes, or the official docs provide enough static metadata to create a non-callable blocked stub.

If any gate fails, block or skip the candidate. Do not deploy partial publisher definitions with guessed auth, guessed endpoints, or guessed billing metadata.

Output Format

Return a concise inline report with these groups:

• deployed: publishers created in this run
• existing: matching publishers already present in the live catalog
• updated: existing publishers changed in this run
• skipped: researched candidates intentionally skipped
• blocked: candidates that could not be safely evaluated or deployed

For each item, include:

• company name
• publisher slug
• official docs URL when available
• auth method
• endpoint family count
• logo status
• validation status
• short reason or next action

Persistence Rules

Do not persist research notes, candidate lists, or run state. The only durable output is the generated or updated publisher definition. Return the run report inline.

Safety Rules

• Do not claim a third-party integration is unavailable without the mandatory live catalog guard.
• Do not create publishers for companies whose APIs are private, invite-only, undocumented, or legally unclear.
• Do not invent pricing, wallet, owner, contact, or Base network settings. Clone the live Asana values for those fields.
• Do not persist anything except the generated publisher definitions.
• Do not deploy a publisher that allows uncatalogued endpoints.

Example

Operator request:

Create publishers for Linear and similar project management tools.

Expected behavior:

1. Call list_agent_publishers with no arguments.
2. Check for an existing linear publisher.
3. Resolve the live Asana publisher template.
4. Research Linear, top 10 competitors, and adjacent category leaders, capped at 20 companies total.
5. Verify each API with Perplexity.
6. Deploy only validated publishers.
7. Return the grouped inline report.