How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

linkedin-company-page - Skill

Name: linkedin-company-page
Author: acedatacloud

Imported from acedatacloud/skills (skills/linkedin-company-page/SKILL.md). Install upstream with npx skills add acedatacloud/skills --skill linkedin-company-page. Copyright stays with the author (Apache-2.0).

LinkedIn company Page

The OAuth token is injected as $LINKEDIN_COMPANY_PAGE_TOKEN. This is a separate connection from the personal LinkedIn connector. The user must supply the numeric organization ID of a Page they administer. The API rejects Pages outside their authorized roles.

The script uses the official versioned Posts API. It defaults to a dry run; --confirm performs the public write. Do not use a cookie or browser fallback.

SCRIPT="$SKILL_DIR/scripts/linkedin_company_page.py"
python3 "$SCRIPT" publish --organization-id 123456 --text-file post.txt
# Show the exact text and target Page to the user before this call:
python3 "$SCRIPT" publish --organization-id 123456 --text-file post.txt --confirm

The confirmed call returns the LinkedIn post URN from x-restli-id, then reads the post back through GET /rest/posts/{urn}. Treat 201 alone as a submitted post, not verified delivery. If the readback fails, report the URN as pending; never retry the write until the existing post's status is established.

LINKEDIN_API_VERSION can override the default monthly API version if LinkedIn retires it. The token and request headers must never be printed.

After a verified public URL is returned, record it once with publish_artifact(kind="article", channel="linkedin-company-page", title="<title>", url="<real URL>", status="delivered").

Official references: Posts API, Organization Access Control.

Install linkedin-company-page and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "acedatacloud-skills-linkedin-company-page", "kind": "skill", "name": "linkedin-company-page", "description": "Draft, publish, and verify a post on a LinkedIn company Page administered by the connected member. Use for an organization's LinkedIn feed, not a personal profile.", "publisher": "acedatacloud", "version": "1.0.0", "capabilities": { "domains": [ "coding", "customer_support" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Draft, publish, and verify a post on a LinkedIn company Page administered by the connected member. Use for an organization's LinkedIn feed, not a personal profile." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/acedatacloud/skills", "path": "skills/linkedin-company-page/SKILL.md", "ref": "HEAD", "url": "https://github.com/acedatacloud/skills/blob/HEAD/skills/linkedin-company-page/SKILL.md", "key": "acedatacloud/skills/skills/linkedin-company-page/SKILL.md" }, "license": "Apache-2.0" }, "instructions": "# LinkedIn company Page\n\nThe OAuth token is injected as `$LINKEDIN_COMPANY_PAGE_TOKEN`. This is a\nseparate connection from the personal LinkedIn connector. The user must supply\nthe numeric organization ID of a Page they administer. The API rejects Pages\noutside their authorized roles.\n\nThe script uses the official versioned Posts API. It defaults to a **dry run**;\n`--confirm` performs the public write. Do not use a cookie or browser fallback.\n\n```bash\nSCRIPT=\"$SKILL_DIR/scripts/linkedin_company_page.py\"\npython3 \"$SCRIPT\" publish --organization-id 123456 --text-file post.txt\n# Show the exact te", "cost": { "context_tokens": 413 } }

linkedin-company-page

About

LinkedIn company Page

Install linkedin-company-page and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews