open-index/open-npm huggingface dataset:
npm package: @shipany/shipany-code
Description: AI coding agent powered by Open Agent SDK. Like Claude Code, but open-source and deployable anywhere.
Author: ShipAny
Latest version: 0.1.0

# ShipAny Code

AI coding agent powered by [Open Agent SDK](https://github.com/shipany-ai/open-agent-sdk). Like Claude Code, but open-source and deployable anywhere.

## Architecture

```
shipany-code (this project) = CLI + Terminal UI
    └── @shipany/open-agent-sdk = Full agent engine (QueryEngine, 26 tools, MCP, etc.)
```

This is the inverse of the official Claude ecosystem:
- Official: `claude-code` (monolith) → `claude-agent-sdk` (thin wrapper)
- Ours: `open-agent-sdk` (full engine) ← `shipany-code` (CLI shell)

## Install

```sh
npm install -g @shipany/shipany-code
```

## Usage

### Interactive mode (REPL)

```sh
shipany-code
```

### Non-interactive mode

```sh
# With -p flag
shipany-code -p "Find and fix the bug in auth.py"

# With pipe
echo "Explain this codebase" | shipany-code

# With options
shipany-code -p "Refactor the API" --model claude-opus-4-6 --max-turns 30
```

### Options

| Option | Description |
|--------|-------------|
| `-v, --version` | Show version |
| `-h, --help` | Show help |
| `-p, --prompt <text>` | Run a one-shot prompt |
| `--model <model>` | Model to use (default: `claude-sonnet-4-6`) |
| `--max-turns <n>` | Maximum agentic turns |
| `--system-prompt <text>` | Custom system prompt |
| `--cwd <path>` | Working directory |

## Development

```sh
# Clone and build
git clone https://github.com/shipany-ai/shipany-code.git
cd shipany-code
npm install
npm run build

# Run locally
node dist/cli.js

# Or with tsx (dev mode)
npx tsx src/cli.ts
```

## License

MIT
npm package: @shipbook/core
Description: Shipbook core SDK - Platform-agnostic logging foundation
Author: Elisha Sterngold
Latest version: 2.0.1

# @shipbook/core

The platform-agnostic core of the Shipbook SDK. This package provides the foundational logging infrastructure used by all Shipbook platform-specific packages.

## ⚠️ Important

**This package is not meant to be used directly.** Instead, use one of the platform-specific packages:

- **[@shipbook/react-native](https://www.npmjs.com/package/@shipbook/react-native)** - For React Native apps
- **[@shipbook/browser](https://www.npmjs.com/package/@shipbook/browser)** - For web/SPA applications
- **[@shipbook/node](https://www.npmjs.com/package/@shipbook/node)** - For Node.js servers and serverless functions

## What's Included

This core package contains:

- **Log Management** - Centralized logging with severity levels (verbose, debug, info, warning, error)
- **Session Management** - User session tracking and configuration
- **Appenders** - Console and cloud appender implementations
- **Models** - Data structures for logs, exceptions, and events
- **Networking** - API client for Shipbook cloud services

## Logging API

All log methods accept multiple arguments (like `console.log`):

```typescript
log.d('Message');                                    // Simple message
log.d('User data:', { id: 123, name: 'John' });     // With object
log.d('Items:', ['a', 'b', 'c']);                    // With array
log.d('Count:', 42, 'Status:', { active: true });   // Multiple args
log.e('Failed', new Error('Something went wrong')); // With error (last arg)
log.e('Context:', { id: 123 }, new Error('Fail'));  // Context + error
```

Error objects should be passed as the **last argument** to be properly captured with stack traces.

## For Package Developers

If you're building a new platform adapter for Shipbook, you'll need to implement the following interfaces:

```typescript
import {
  IStorage,
  IPlatform,
  IEventManager,
  IExceptionHandler,
} from '@shipbook/core';
```

### Required Interfaces

- **IStorage** - Persistent key-value storage
- **IPlatform** - Platform information (OS, version, device info)
- **IEventManager** - Lifecycle event handling (foreground/background)
- **IExceptionHandler** - Uncaught exception capture

See the existing adapters in [@shipbook/react-native](https://github.com/ShipBook/shipbook-js/tree/master/packages/react-native), [@shipbook/browser](https://github.com/ShipBook/shipbook-js/tree/master/packages/browser), or [@shipbook/node](https://github.com/ShipBook/shipbook-js/tree/master/packages/node) for reference implementations.

## Links

- [Shipbook Website](https://www.shipbook.io/)
- [GitHub Repository](https://github.com/ShipBook/shipbook-js)
- [Documentation](https://docs.shipbook.io/)

## License

MIT
npm package: @shipclub/plan-mcp
Description: MCP server that helps an LLM plan and stay on track by saving and injecting context.
Latest version: 0.0.7

# `plan-mcp`

MCP server that helps an LLM plan and stay on track by saving and injecting context.

## Tools

- `get-plan` gets the current plan
- `add-tasks-to-plan` adds tasks to the end of the current plan
- `get-next-task` will mark the current task as done, and mark the next task as in progress

## Get started

Add this as an MCP tool with `npx` for example in Cursor `.cursor/mcp.json`:

```json
{
    "mcpServers": {
        "plan": {
            "command": "npx",
            "args": [
                "-y",
                "@shipclub/plan-mcp@latest"
            ],
            "env": {
                "SHIPCLUB_PROJECT_PATH": "/Users/your-user/code/your-project"
            }
        }
    }
}
```

## Project path

`SHIPCLUB_PROJECT_PATH` will specify where a `.shipclub` directory should be created.

This is used to store a markdown representation of the tasks that can be edited in `.shipclub/tasks`.

## Triggers

Optionally a trigger can be added in `.shipclub/triggers/task-completed`

This will run when next task is called and needs to pass before the LLM is given the next task. e.g. to run typechecks before moving on.

Make sure to `chmod +x` the `task-completed` trigger.

## Analytics

`plan-mcp` collects anonymised usage and meta data with Posthog -- this doesn't include your plan or task information.

This is used to inform what is working (and not) to try and make it better in future.

For example, this includes:
- Add tasks and the number of tasks added
- The current status of tasks
- Calls to next task, and if a trigger run fails

This MCP server won't send us code or task text.

You can opt out by setting `SHIPCLUB_NO_ANONYMISED_ANALYTICS` to `1`.

## TODO

- [X] Add tasks
- [X] Get plan
- [X] Get next task (updating the current task to done)
- [X] Add lifecycle hooks
- [ ] Add subtasks
- [ ] Add dependencies
- [ ] Edit tasks
npm package: @shipdeckai/claude-skills
Description: A curated collection of Claude Code skills and plugins for AI-powered development workflows
Author: Shipdeckai
Latest version: 1.0.2

# Claude Skills

A curated collection of Claude Code skills and plugins for AI-powered development workflows.

## Available Skills

| Skill | Description |
|-------|-------------|
| [image-gen](https://github.com/shipdeckai/image-gen) | AI image generation and editing across multiple providers |

## Installation

Install skills directly in Claude Code:

```bash
# Add this marketplace
/plugin marketplace add https://github.com/shipdeckai/claude-skills

# Install a skill
/plugin install image-gen@claude-skills
```

## Contributing

Want to add your skill to the marketplace? Open a PR adding your skill to `.claude-plugin/marketplace.json`.

## License

MIT
npm package: @shipem/mcp
Description: Shipem MCP server — deploy from any AI assistant
Author: Shipem
Latest version: 0.1.2

# @shipem/mcp

MCP server for Shipem — deploy web apps directly from Claude Desktop, Cursor, or any MCP-compatible AI tool.

## Setup (Claude Desktop)

Add to `~/Library/Application Support/Claude/claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "shipem": {
      "command": "npx",
      "args": ["-y", "@shipem/mcp"],
      "env": {
        "CLOUDFLARE_API_TOKEN": "your_cf_token",
        "CLOUDFLARE_ACCOUNT_ID": "your_account_id"
      }
    }
  }
}
```

Get CF credentials: https://dash.cloudflare.com/profile/api-tokens
- Token needs: Cloudflare Pages (Edit) permission
- Account ID: found on CF dashboard right sidebar

## Tools

| Tool | Description |
|------|-------------|
| `shipem_deploy` | Deploy a project to a live URL |
| `shipem_fix` | Auto-fix build errors |
| `shipem_init` | Scaffold a new project |
| `shipem_scan` | Detect framework + build config |
| `shipem_status` | Get deployment URL + history |
| `shipem_env` | Scan for missing env vars |

## Example prompts

- "Deploy this project" → Claude calls `shipem_deploy`
- "My build is failing, fix it" → Claude calls `shipem_fix`
- "Create a new Vite app called dashboard" → Claude calls `shipem_init`
- "What's the URL of my deployed app?" → Claude calls `shipem_status`

## Resources

- `shipem://project` — current project config
- `shipem://deployments` — deployment history

## Requirements

- Node.js 18+
- Cloudflare account (free tier works)
- `CLOUDFLARE_API_TOKEN` and `CLOUDFLARE_ACCOUNT_ID` env vars