open-index/open-npm huggingface dataset:
npm package: @gekkocompany/orchestra
Description: OpenClaw plugin runtime for the `/orch` command. Handles blueprint loading, session state, and multi-step orchestration as defined in the Orchestra specification.
Author: Gekko Company
Latest version: 0.3.22

## Orchestra Engine

**Orchestra** is an OpenClaw plugin that powers the `/orch` slash command. It loads Markdown blueprints, lets the LLM/agent pick the right blueprint for a user brief, and hands the full workflow off to an isolated agent session.


### What you can do with `/orch`

At a high level, blueprints can support scenarios like:

- **Content creation** (for example: `/orch Create a blog post about plant based protein`)
- **Research flows** (for example: `/orch Research the latest trends in electric vehicles`)
- **Other multi-step workflows** that are encoded as blueprints (tweets, reports, summaries, etc.)

The exact workflows available depend on the blueprints present in your configured repositories and how they are described in their `blueprint-index.md` files.

### Prerequisites

- **OpenClaw gateway** `>= 0.7` with slash commands and skills enabled.
- **Orchestra plugin installed** on the gateway, your OpenClaw admin should run `openclaw plugins install @gekkocompany/orchestra`.
- **Blueprint repositories**  Use the command `/orch blueprints init [project?] gitRepo [gitPAT?]` to install your blueprint repository on the gateway correctly, for example: `Orchestra/repos/acme-content-blueprints` containing `blueprint-index.md` and `./blueprints/*.md` blueprints.  

### Using `/orch`

#### status
```text
/orch status
```
Checks orchestra status

#### run
```text
/orch [project?] <brief>
```
Finds and starts the blueprint to create your artifact 

#### abort
```text
/orch abort
```
Stops the currently running blueprint.

#### blueprints init
```text
/orch blueprints init [project?] <gitRepo> [gitPAT?]
```
Initializes a blueprint project by cloning its repository into the Orchestra workspace.

#### blueprints add
```text
/orch blueprints [project?] add <brief>
```
Guides you through creating and saving a new blueprint in the selected project.

#### blueprints update
```text
/orch blueprints [project?] update <blueprint name>
```
Requests an update to an existing blueprint;  -- currently this command is not yet implemented.

#### blueprints refresh
```text
/orch blueprints [project?] refresh
```
Refreshes a project’s blueprints so they are up to date with their remote repository.
npm package: @gekorm/date-fns-types
Description: Modern JavaScript date utility library
Latest version: 2.30.0

<p align="center">
  <a href="https://date-fns.org/">
    <img alt="date-fns" title="date-fns" src="https://raw.githubusercontent.com/date-fns/date-fns/master/docs/logotype.svg" width="300" />
  </a>
</p>

<p align="center">
  <b>date-fns</b> provides the most comprehensive, yet simple and consistent toolset
  <br>
  for manipulating <b>JavaScript dates</b> in <b>a browser</b> & <b>Node.js</b>.</b>
</p>

<div align="center">

[📖&nbsp; Documentation](https://date-fns.org/docs/Getting-Started/)&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;[🧑‍💻&nbsp; JavaScript Jobs](https://jobs.date-fns.org/)

</div>

<hr>

# It's like [Lodash](https://lodash.com) for dates

- It has [**200+ functions** for all occasions](https://date-fns.org/docs/Getting-Started/).
- **Modular**: Pick what you need. Works with webpack, Browserify, or Rollup and also supports tree-shaking.
- **Native dates**: Uses existing native type. It doesn't extend core objects for safety's sake.
- **Immutable & Pure**: Built using pure functions and always returns a new date instance.
- **TypeScript & Flow**: Supports both Flow and TypeScript
- **I18n**: Dozens of locales. Include only what you need.
- [and many more benefits](https://date-fns.org/)

```js
import { compareAsc, format } from 'date-fns'

format(new Date(2014, 1, 11), 'yyyy-MM-dd')
//=> '2014-02-11'

const dates = [
  new Date(1995, 6, 2),
  new Date(1987, 1, 11),
  new Date(1989, 6, 10),
]
dates.sort(compareAsc)
//=> [
//   Wed Feb 11 1987 00:00:00,
//   Mon Jul 10 1989 00:00:00,
//   Sun Jul 02 1995 00:00:00
// ]
```

The library is available as an [npm package](https://www.npmjs.com/package/date-fns).
To install the package run:

```bash
npm install date-fns --save
# or with yarn
yarn add date-fns
```

## Docs

[See date-fns.org](https://date-fns.org/) for more details, API,
and other docs.

<br />
<!-- END OF README-JOB SECTION -->

## License

[MIT © Sasha Koss](https://kossnocorp.mit-license.org/)
npm package: @gekorm/hono-openapi
Description: OpenAPI schema generator for Hono
Latest version: 1.1.3

# Form of Hono OpenAPI for Zod v4

[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/rhinobase/hono-openapi)
[![npm version](https://img.shields.io/npm/v/hono-openapi.svg)](https://npmjs.org/package/hono-openapi "View this project on NPM")
[![npm downloads](https://img.shields.io/npm/dm/hono-openapi)](https://www.npmjs.com/package/hono-openapi)

This can automatically generate the OpenAPI specification for the Hono App using your validation schema, which can be used to generate client libraries, documentation, and more.

This lib supports all the validation libs which are [Standard Schema](https://standardschema.dev/) compliant.

For documentation visit [honohub.dev](https://honohub.dev).

> [!Note]
> This package is still in development and your feedback is highly appreciated. If you have any suggestions or issues, please let us know by creating an issue on GitHub.

## Contributing

Visit our [contributing docs](https://github.com/rhinobase/hono-openapi/blob/main/CONTRIBUTING.md).

## Credits

- The idea for this project was inspired by [ElysiaJS](https://elysiajs.com/) and their amazing work on generating [OpenAPI](https://elysiajs.com/patterns/openapi) specifications.
- This project would not have been possible without the work of [Sam Chung](https://github.com/samchungy) and his [Zod OpenAPI](https://github.com/samchungy/zod-openapi) package.
npm package: @gekorm/kysely-tables
Description: Use the same Kysely types for your SQL table schema, migrations and queries.
Author: Jonas Galvez
Latest version: 0.1.3

# kysely-tables

<br><img width="492" src="https://hire.jonasgalvez.com.br/kt.png" />

<br>Use the **same Kysely types** for your **SQL table schema**, **migrations** and **queries**.

- No need for an intermediary [schema defining API](https://orm.drizzle.team/docs/schemas) or [schema language](https://www.prisma.io/docs/orm/prisma-schema/overview).
- No need to [connect to the database to retrieve the schema structure](https://github.com/RobinBlomberg/kysely-codegen).
- No need to [bloat](https://github.com/drizzle-team/drizzle-kysely) [your](https://github.com/eoin-obrien/prisma-extension-kysely) [setup](https://github.com/valtyr/prisma-kysely) mixing multiple database libraries.

**Your Kysely types** become the **single source of truth** for your `CREATE TABLE` statements.

**And also** for **creating and running migrations**, very much like Prisma and Drizzle.

[**See the full README on GitHub**](https://github.com/galvez/kysely-tables/blob/main/README.md).

## License

MIT
npm package: @gekorm/standard-openapi
Description: [![npm version](https://img.shields.io/npm/v/@standard-community/standard-openapi.svg)](https://npmjs.org/package/@standard-community/standard-openapi "View this project on NPM") [![npm downloads](https://img.shields.io/npm/dm/@standard-community/standar
Latest version: 0.2.9

# Fork of Standard OpenAPI for Zod v4

[![npm version](https://img.shields.io/npm/v/@standard-community/standard-openapi.svg)](https://npmjs.org/package/@standard-community/standard-openapi "View this project on NPM")
[![npm downloads](https://img.shields.io/npm/dm/@standard-community/standard-openapi)](https://www.npmjs.com/package/@standard-community/standard-openapi)
[![license](https://img.shields.io/npm/l/@standard-community/standard-openapi)](LICENSE)

Standard Schema Validator's OpenAPI Schema Converter

## Installation

Install the main package -

```sh
pnpm add @standard-community/standard-openapi
```

For some specific vendor, install the respective package also -

| Vendor  | Package |
| ------- | ------- |
| Zod v3  | `zod-openapi@4` |
| Valibot | `@valibot/to-json-schema` |

## Usage

```ts
import { toOpenAPISchema } from "@standard-community/standard-openapi";

// Define your schema
const schema = v.pipe(
    v.object({
        myString: v.string(),
        myUnion: v.union([v.number(), v.boolean()]),
    }),
    v.description("My neat object schema"),
);

// Convert it to OpenAPI Schema
const openapiSchema = await toOpenAPISchema(schema);
```

### Sync Usage

#### Adding support for Unsupported validation libs

```ts
import { toOpenAPISchema, loadVendor } from "@standard-community/standard-openapi";
import { convertSchemaToJson } from "your-validation-lib";

// The lib should support Standard Schema, like Sury
// as we use 'schema["~standard"].vendor' to get the vendor name
// Eg. loadVendor(zod["~standard"].vendor, convertorFunction)
loadVendor("validation-lib-name", convertSchemaToJson)

// Define your validation schema
const schema = {
    // ...
};

// Convert it to OpenAPI Schema
const openapiSchema = toOpenAPISchema(schema);
```

#### Customize the toOpenAPISchema of a supported lib

```ts
import { z } from "zod/v4";
import { toJSONSchema } from "zod/v4/core";
import { toOpenAPISchema, loadVendor } from "@standard-community/standard-openapi";
import { convertToOpenAPISchema } from "@standard-community/standard-openapi/convert";

// Or pass a custom implmentation
loadVendor("zod", (schema, context) => {
    return convertToOpenAPISchema(toJSONSchema(schema, {
        io: "input"
    }), context);
})

// Define your schema
const schema = z.object({
    myString: z.string(),
    myUnion: z.union([z.number(), z.boolean()]),
}),

// Convert it to OpenAPI Schema
const openapiSchema = await toOpenAPISchema(schema);
```