open-index/open-npm huggingface dataset:
npm package: @open-agent-studio/plugin-apify
Description: Unified Apify plugin for Open Agent Studio — run Actors, manage datasets, and orchestrate web scraping from your AI agent
Author: Open Agent Studio
Latest version: 1.0.0

# @open-agent-studio/plugin-apify

Official Apify integration plugin for [Open Agent Studio](https://openagent.studio). Run web scrapers, manage datasets, and orchestrate 2,000+ Apify Actors from your AI agent.

## Installation

```bash
agent plugins install @open-agent-studio/plugin-apify
```

## Setup

1. Create a free account at [apify.com](https://apify.com)
2. Get your API token: Profile → Settings → Integrations → Personal API Token
3. Save it:

```bash
agent credentials set APIFY_API_TOKEN "apify_api_your_token_here"
```

## Usage

### Natural Language
```bash
agent "Scrape all product prices from example-store.com"
agent "Search Apify Store for a Google Maps scraper and run it"
agent "Schedule a daily scrape of competitor pricing"
```

### CLI Commands
```bash
agent apify run apify/web-scraper --input '{"startUrls":[{"url":"https://example.com"}]}' --sync
agent apify store "instagram scraper"
agent apify actors
agent apify status <run-id>
agent apify results <dataset-id> --format csv
agent apify datasets
```

## Tools Registered

| Tool | Description |
|------|-------------|
| `apify.run` | Run an Apify Actor (async or sync) |
| `apify.status` | Check run status |
| `apify.results` | Get dataset results |
| `apify.actors` | List/get your Actors |
| `apify.store` | Search the Apify Store |
| `apify.datasets` | List/manage datasets |
| `apify.schedule` | Create/manage cron schedules |
| `apify.kv` | Key-Value Store operations |

## Security

Your API token is encrypted with AES-256-GCM and stored locally in `vault.json`. It never leaves your machine.

## License

MIT © Open Agent Studio
npm package: @open-agent-studio/plugin-social
Description: Unified Social Media plugin for Open Agent Studio — post to LinkedIn, X, Meta, and Instagram from your AI agent
Author: Open Agent Studio
Latest version: 1.0.0

# @open-agent-studio/plugin-social

> **Unified Social Media Plugin** — Post to LinkedIn, X/Twitter, Facebook, and Instagram from your autonomous AI agent.

## Installation

```bash
agent plugins install @open-agent-studio/plugin-social
```

Or manually copy to `.agent/plugins/social/` in your project.

## Quick Start

### 1. Set Up Platform Credentials

Before authenticating, you need developer app credentials for each platform. Store them in your credential vault:

```bash
# LinkedIn
agent credentials set SOCIAL_LINKEDIN_CLIENT_ID "your-client-id"
agent credentials set SOCIAL_LINKEDIN_CLIENT_SECRET "your-client-secret"

# X/Twitter
agent credentials set SOCIAL_TWITTER_CLIENT_ID "your-client-id"
agent credentials set SOCIAL_TWITTER_CLIENT_SECRET "your-client-secret"

# Meta (Facebook + Instagram)
agent credentials set SOCIAL_META_CLIENT_ID "your-app-id"
agent credentials set SOCIAL_META_CLIENT_SECRET "your-app-secret"
```

### 2. Authenticate

```bash
agent social auth linkedin
agent social auth twitter
agent social auth facebook
agent social auth instagram
```

Each command opens a browser window for OAuth authorization.

### 3. Post Content

```bash
# Post to a single platform
agent social post -p linkedin -t "Shipping v1.0 today! 🚀"

# Post to multiple platforms
agent social post -p linkedin,twitter -t "Hello from Open Agent Studio!" --tags "ai,automation"

# Post with an image
agent social post -p instagram -t "Our new feature" -i "https://example.com/image.png"
```

### 4. Use with Natural Language

```bash
agent "Post a summary of today's code changes to LinkedIn and Twitter"
```

The agent will automatically use the `social-poster` skill to format and publish content.

## Supported Platforms

| Platform | Text | Images | Links | Threads | Auth |
|----------|:----:|:------:|:-----:|:-------:|:----:|
| LinkedIn | ✅ | ✅ | ✅ | — | OAuth 2.0 |
| X/Twitter | ✅ | ✅ | ✅ | 🔜 | OAuth 2.0 (PKCE) |
| Facebook | ✅ | ✅ | ✅ | — | OAuth 2.0 |
| Instagram | — | ✅ | — | — | OAuth 2.0 (Meta) |

## Security

- All OAuth tokens are stored in your local AES-256 encrypted vault (`vault.json`)
- Tokens never leave your machine
- You can revoke access at any time through each platform's settings
- See our [Privacy Policy](https://openagent.studio/privacy) and [Terms](https://openagent.studio/terms)

## License

MIT
npm package: @open-agent-toolkit/cli
Description: Open Agent Toolkit CLI
Latest version: 0.0.28

# @open-agent-toolkit/cli

Open Agent Toolkit command-line interface for provider sync, docs tooling, workflow utilities, and diagnostics.

## Install

```bash
npm install -g @open-agent-toolkit/cli
```

Run without a global install:

```bash
npx @open-agent-toolkit/cli --help
```

## Quick Start

```bash
oat init --scope project
oat status --scope all
oat sync --scope all
oat config describe
```

Additional useful entry points:

- `oat tools install`
- `oat docs init --app-name my-docs`
- `oat config dump --json`
- `oat project status --json`
- `oat project list --json`
- `oat project archive sync`
- `oat doctor`

## Inspection Commands

Use these commands when you want structured runtime/project state out of the CLI:

- `oat config dump --json` - emit merged OAT config with per-key source attribution
- `oat project status --json` - emit the active project's full parsed control-plane state
- `oat project list --json` - emit summary state for tracked projects under the configured projects root

## Requirements

- Node.js `>=22.17.0`

## Docs

- [Docs Home](https://voxmedia.github.io/open-agent-toolkit/)
- [CLI Utilities](https://voxmedia.github.io/open-agent-toolkit/cli-utilities)
- [Provider Sync](https://voxmedia.github.io/open-agent-toolkit/provider-sync)
- [Reference](https://voxmedia.github.io/open-agent-toolkit/reference)
npm package: @open-agent-toolkit/control-plane
Description: Read-only OAT control-plane library for structured project state
Latest version: 0.0.28

# @open-agent-toolkit/control-plane

Read-only OAT control-plane library for parsing project artifacts into structured state.

## Purpose

`@open-agent-toolkit/control-plane` is the typed "read" layer behind OAT project inspection.

It is responsible for:

- parsing OAT project artifacts from disk
- aggregating task progress, artifact status, and review state
- recommending the next workflow skill from parsed project state
- returning stable typed objects for CLI and future UI consumers

The package is intentionally pure and read-only. It has no CLI, UI, or server dependencies beyond Node.js filesystem/path builtins and `yaml` for frontmatter parsing.

## Public API

```ts
import {
  getProjectState,
  listProjects,
  recommendSkill,
} from '@open-agent-toolkit/control-plane';
```

### `getProjectState(projectPath)`

Reads one OAT project directory and returns a full `ProjectState` snapshot, including:

- phase and lifecycle status
- task progress and current task
- artifact and review status
- blocker and HiLL metadata
- PR/docs timestamps and recommendation output

### `listProjects(projectsRoot)`

Reads all projects under a configured projects root and returns lightweight `ProjectSummary` records suitable for list or dashboard surfaces.

### `recommendSkill(projectState)`

Pure function that maps parsed project state to the next recommended OAT workflow skill.

## Current Consumers

- `packages/cli/src/commands/project/status.ts`
- `packages/cli/src/commands/project/list.ts`

The CLI also uses adjacent config-resolution code for `oat config dump`, but the control plane remains focused on project artifact parsing rather than config ownership.

## Development

```bash
pnpm --filter @open-agent-toolkit/control-plane test
pnpm --filter @open-agent-toolkit/control-plane lint
pnpm --filter @open-agent-toolkit/control-plane type-check
pnpm --filter @open-agent-toolkit/control-plane build
```
npm package: @open-agent-toolkit/docs-config
Description: Configuration factories for OAT documentation sites
Latest version: 0.0.28

# @open-agent-toolkit/docs-config

Configuration helpers for OAT-powered Fumadocs apps.

## Install

```bash
pnpm add @open-agent-toolkit/docs-config @open-agent-toolkit/docs-theme @open-agent-toolkit/docs-transforms
```

Install the required Fumadocs, Next.js, and React peer dependencies in your app as well.

## Usage

`next.config.js`

```js
import { createDocsConfig } from '@open-agent-toolkit/docs-config';

export default createDocsConfig({
  title: 'My Docs',
  description: 'Documentation site',
});
```

`source.config.ts`

```ts
import { createSourceConfig } from '@open-agent-toolkit/docs-config';
import { defineConfig, defineDocs } from 'fumadocs-mdx/config';

const sourceConfig = createSourceConfig();

export const docs = defineDocs({
  dir: sourceConfig.contentDir,
});

export default defineConfig({
  mdxOptions: {
    remarkPlugins: sourceConfig.remarkPlugins,
  },
});
```

## Exports

- `createDocsConfig`
- `createSearchConfig`
- `createSourceConfig`

## Docs

- [Docs Tooling](https://voxmedia.github.io/open-agent-toolkit/docs-tooling)
- [Repository](https://github.com/voxmedia/open-agent-toolkit)
npm package: @open-agent-toolkit/docs-theme
Description: Theme components for OAT documentation sites
Latest version: 0.0.28

# @open-agent-toolkit/docs-theme

Shared React components for OAT-powered Fumadocs apps.

## Install

```bash
pnpm add @open-agent-toolkit/docs-theme
```

Install the required Fumadocs and React peer dependencies in your app as well.

## Usage

```tsx
import {
  DocsLayout,
  DocsPage,
  Mermaid,
  Tab,
  Tabs,
} from '@open-agent-toolkit/docs-theme';

export function Layout({ tree, children }) {
  return (
    <DocsLayout branding={{ title: 'My Docs' }} tree={tree}>
      {children}
    </DocsLayout>
  );
}

export function Page({ toc, chart }) {
  return (
    <DocsPage toc={toc}>
      <Tabs>
        <Tab title='Diagram'>
          <Mermaid chart={chart} />
        </Tab>
      </Tabs>
    </DocsPage>
  );
}
```

## Exports

- `DocsLayout`
- `DocsPage`
- `Mermaid`
- `Tab`
- `Tabs`

## Docs

- [Docs Tooling](https://voxmedia.github.io/open-agent-toolkit/docs-tooling)
- [Repository](https://github.com/voxmedia/open-agent-toolkit)
npm package: @open-agent-toolkit/docs-transforms
Description: Remark/unified transforms for OAT documentation
Latest version: 0.0.28

# @open-agent-toolkit/docs-transforms

Remark plugins and default transform bundle for OAT-powered Fumadocs apps.

## Install

```bash
pnpm add @open-agent-toolkit/docs-transforms
```

## Usage

```ts
import {
  defaultTransforms,
  remarkLinks,
  remarkMermaid,
  remarkTabs,
} from '@open-agent-toolkit/docs-transforms';

export const remarkPlugins = defaultTransforms;

export const customRemarkPlugins = [remarkLinks, remarkTabs, remarkMermaid];
```

## Exports

- `defaultTransforms`
- `remarkLinks`
- `remarkMermaid`
- `remarkTabs`

## Docs

- [Docs Tooling](https://voxmedia.github.io/open-agent-toolkit/docs-tooling)
- [Repository](https://github.com/voxmedia/open-agent-toolkit)
npm package: @open-agreements/checklist-mcp
Description: Local stdio MCP server for OpenAgreements checklist memory operations
Latest version: 0.7.5

# @open-agreements/checklist-mcp

Local stdio MCP server for OpenAgreements closing checklist operations.

Provides tools for creating, reading, updating, rendering, and diffing closing checklists via the Model Context Protocol.

## Installation

```bash
npx -y @open-agreements/checklist-mcp
```

Or add to your MCP client config:

```json
{
  "mcpServers": {
    "checklist-mcp": {
      "command": "npx",
      "args": ["-y", "@open-agreements/checklist-mcp"]
    }
  }
}
```

## Tools

- `checklist_create` — Create a new closing checklist
- `checklist_read` — Read checklist state
- `checklist_update` — Apply JSON Patch operations
- `checklist_render_docx` — Render checklist as formatted DOCX
- `checklist_diff` — Import DOCX and diff against canonical state

## License

MIT
npm package: @open-agreements/contract-templates-mcp
Description: Local stdio MCP server for OpenAgreements template discovery and filling
Latest version: 0.7.5

# @open-agreements/contract-templates-mcp

Local stdio MCP server for OpenAgreements template discovery and drafting.

## Scope

This package exposes local template tools over MCP:

- `list_templates`
- `get_template`
- `fill_template`

It is intentionally separate from `@open-agreements/contracts-workspace-mcp`,
which focuses on repository/workspace organization and catalog/status workflows.

## Local Run

From this repository:

```bash
npm run build:contract-templates-mcp
node packages/contract-templates-mcp/bin/open-agreements-contract-templates-mcp.js
```

## Gemini CLI Local MCP Example

```json
{
  "mcpServers": {
    "contract-templates-mcp": {
      "command": "npx",
      "args": ["-y", "@open-agreements/contract-templates-mcp"]
    }
  }
}
```
npm package: @open-agreements/contracts-workspace-mcp
Description: Local stdio MCP server for contracts workspace operations
Latest version: 0.7.5

# @open-agreements/contracts-workspace-mcp

Local stdio MCP server for contracts workspace operations.

## Scope

This package exposes local workspace tools (topic-first init planning, catalog, status) over MCP so
agents can operate on a local contracts directory without a remote server.

## Available Tools

- `workspace_init`
- `catalog_validate`
- `catalog_fetch`
- `status_generate`
- `status_lint`

## Local Run

From this repository:

```bash
npm run build:workspace-mcp
node packages/contracts-workspace-mcp/bin/open-agreements-workspace-mcp.js
```

## Claude Code Local MCP Setup

```bash
claude mcp add --transport stdio open-agreements-workspace-mcp -- node /ABSOLUTE/PATH/TO/open-agreements/packages/contracts-workspace-mcp/bin/open-agreements-workspace-mcp.js
```

Then in Claude Code, call tools like:

- `workspace_init` with `{"root_dir":"/path/to/workspace","agents":["claude","gemini"]}` to get missing folder/file suggestions (no auto-write)
- `status_generate` with `{"root_dir":"/path/to/workspace"}`

## Claude Desktop Local Connector Setup

Configure a local stdio MCP server using the same command and absolute path:

- command: `node`
- args: `[/ABSOLUTE/PATH/TO/open-agreements/packages/contracts-workspace-mcp/bin/open-agreements-workspace-mcp.js]`

Use a local directory for `root_dir` parameters (including locally synced Google
Drive folders).
npm package: @open-alchemy/editor-sdk
Description: An SDK for interacting with the OpenAlchemy editor service.
Author: David Andersson
Latest version: 0.1.10

# OpenAlchemy Editor SDK

An SDK for interacting with the OpenAlchemy editor service.

For API based interactions check here:
<https://editor.api.openalchemy.io/v1/ui/>

## Getting Started

To validate a spec:

```typescript
import { SpecService } from '@open-alchemy/editor-sdk';

const service = new SpecsService();
// Validate the managed portion of a spec
const result = await service.validateManaged({
  value: '<an OpenAlchemy OpenAPI Spec in YAML>',
  language: 'YAML',
});
// Validate the un managed portion of a spec
const result = await service.validateManaged({
  value: '<an OpenAlchemy OpenAPI Spec in JSON>',
  language: 'JSON',
});
```

To calculate the artifacts of spec:

```typescript
import { ArtifactService } from '@open-alchemy/editor-sdk';

const service = new ArtifactService();
const artifacts = await service.calculate({
  value: '<an OpenAlchemy OpenAPI Spec in YAML>',
  language: 'YAML',
});
```

To retrieve seeds:

```typescript
import { SeedService } from '@open-alchemy/editor-sdk';

const service = new SeedService();
// To retrieve the default seed
const defaultSeed = await service.getDefault();
// To retrieve all available seed
const availableSeeds = await service.list();
// To retrieve a particular seed
const seed = await service.get({ path: availableSeeds[0].path });
```

## CI-CD

The workflow for the CI-CD is defined here:
[../.github/workflows/ci-cd-sdk.yaml](../.github/workflows/ci-cd-sdk.yaml).

## Production Tests

The tests against the sdk package are defined here:
[../test/sdk/](../test/sdk/).

The workflow that periodically executes the tests is defined here:
[../.github/workflows/production-test-sdk.yaml](../.github/workflows/production-test-sdk.yaml).
npm package: @open-alchemy/package-sdk
Description: An SDK for interacting with the OpenAlchemy package service.
Author: David Andersson
Latest version: 5.0.0

# OpenAlchemy Package SDK

An SDK for interacting with the OpenAlchemy package service.

For API based interactions check here:
<https://package.api.openalchemy.io/v1/ui/>

## Getting Started

To list all available specs:

```typescript
import { SpecsService } from '@open-alchemy/package-sdk';

const service = new SpecsService();
const allSpecs = await service.list({ accessToken });
```

To interact with a particular spec:

```typescript
import { SpecService } from '@open-alchemy/package-sdk';

const service = new SpecService();
// Get the value of a spec
const employeeSpec = await service.get({ accessToken, id: 'employee' });
// Get the value of a particular version of a spec
const employeeSpec = await service.get({
  accessToken,
  id: 'employee',
  version: 'version 1',
});
// Create or update a spec
await service.put({
  accessToken,
  id: 'employee',
  specValue: '<an OpenAlchemy OpenAPI Spec>',
});
// Create or update specific version of a spec
await service.put({
  accessToken,
  id: 'employee',
  specValue: '<an OpenAlchemy OpenAPI Spec>',
  version: 'version 1',
});
// Delete a spec
await service.delete({ accessToken, id: 'employee' });
// List the versions of a spec
const specVersions = await service.getVersions({
  accessToken,
  id: 'employee',
});
```

To retrieve credentials:

```typescript
import { CredentialsService } from '@open-alchemy/package-sdk';

const service = new CredentialsService();
// Get the value of credentials
const employeeSpec = await service.get({ accessToken });
// Delete credentials
await service.delete({ accessToken });
```

## CI-CD

The workflow for the CI-CD is defined here:
[../.github/workflows/ci-cd-sdk.yaml](../.github/workflows/ci-cd-sdk.yaml).

## Production Tests

The tests against the sdk package are defined here:
[../test/sdk/](../test/sdk/).

The workflow that periodically executes the tests is defined here:
[../.github/workflows/production-test-sdk.yaml](../.github/workflows/production-test-sdk.yaml).