@claudein.org/cli 0.1.16 → 0.1.17

package/dist/index.js

@@ -25619,8 +25619,10 @@ function positional(schema, index, meta3) {
 // src/index.ts
 import crypto from "crypto";
 import { watch } from "fs";
-import { readFile, writeFile } from "fs/promises";
+import { cp, mkdir, readdir as readdir2, readFile, writeFile } from "fs/promises";
 import { createRequire as createRequire2 } from "module";
+import { homedir } from "os";
+import { dirname as dirname2, join as join2 } from "path";
 
 // ../node_modules/.bun/nanostores@1.3.0/node_modules/nanostores/clean-stores/index.js
 var clean = Symbol("clean");
@@ -26271,6 +26273,7 @@ var $visit = visit.visit;
 var $visitAsync = visit.visitAsync;
 
 // src/index.ts
+import { fileURLToPath as fileURLToPath2 } from "url";
 var { version: version2 } = createRequire2(import.meta.url)("../package.json");
 var DOMAIN = process.env.CIN_ENV === "dev" ? "localhost:3000" : "claudein.org";
 function hash2(post) {
@@ -26371,6 +26374,21 @@ var start = command("start").meta({
 var versionCmd = command("version").meta({ description: "Print the version number" }).action(() => {
   console.log(generateVersion("cin", version2));
 });
+var skillsInstallCmd = command("install").meta({ description: "Install claudein skills into ~/.claude/skills/" }).action(async () => {
+  const pkgRoot = join2(dirname2(fileURLToPath2(import.meta.url)), "..");
+  const skillsDir = join2(pkgRoot, "skills");
+  const targetBase = join2(homedir(), ".claude", "skills");
+  await mkdir(targetBase, { recursive: true });
+  const entries = await readdir2(skillsDir, { withFileTypes: true });
+  for (const entry of entries) {
+    if (!entry.isDirectory())
+      continue;
+    const dst = join2(targetBase, entry.name);
+    await cp(join2(skillsDir, entry.name), dst, { recursive: true });
+    console.log(fmt.success(`Installed ${entry.name} → ${dst}`));
+  }
+});
+var skillsCmd = command("skills").meta({ description: "Manage Claude Code skills" }).use(skillsInstallCmd);
 var cinRef;
 var completionCmd = command("completion").meta({
   description: "Generate shell completion script",
@@ -26380,7 +26398,7 @@ var completionCmd = command("completion").meta({
 }).action(({ inputs: { shell } }) => {
   console.log(generateCompletionScript(cinRef._config, shell));
 });
-cinRef = cli("cin", { version: version2 }).use(start).use(versionCmd).use(completionCmd);
+cinRef = cli("cin", { version: version2 }).use(start).use(skillsCmd).use(versionCmd).use(completionCmd);
 cinRef.run();
 export {
   hash2 as hash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@claudein.org/cli",
-  "version": "0.1.16",
+  "version": "0.1.17",
   "description": "Post to LinkedIn from the command line",
   "type": "module",
   "repository": {
@@ -15,7 +15,8 @@
     "provenance": true
   },
   "files": [
-    "dist"
+    "dist",
+    "skills"
   ],
   "scripts": {
     "build": "bun build src/index.ts --target=node --outfile=dist/index.js",

package/skills/claudein/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: claudein
+description: Create LinkedIn posts using the claudein CLI. Use when the user wants to write, draft, or schedule LinkedIn posts, or when working with any .yml posts file.
+allowed-tools: Edit, Write, Bash(cin *), Bash(pgrep *)
+---
+
+# claudein — LinkedIn posts from the CLI
+
+## Live schema
+
+Read the current schema before writing any posts file — do not rely on memory:
+
+!`curl -s https://raw.githubusercontent.com/claudein-org/main/refs/heads/main/claudein.schema.yml`
+
+## Posts file
+
+The default file is `posts.yml` but users can use any `.yml` file (pass it to `cin start my-posts.yml`). Write to whichever file the user specifies or is already working with.
+
+`cin start` watches the file for changes and updates the browser preview live — always edit the file in place, never delete and recreate it.
+
+## Workflow
+
+1. Write or edit the `.yml` posts file
+2. Check if `cin start` is already running: `pgrep -fa "cin start"` — if it is, skip step 3
+3. If not running: `cin start [file]` — opens the live browser preview
+4. Click "Post" in the browser to publish to LinkedIn
+
+## Media guidelines (LinkedIn)
+
+When generating or sourcing images and videos (e.g. with Remotion), target LinkedIn's specs:
+
+**Images:** 1200×627 px (1.91:1 landscape) or 1080×1080 px (1:1 square) — PNG or JPG, high resolution
+
+**Videos:** MP4, H.264, at least 1280×720 px, 16:9 aspect ratio — up to 4096×2304 supported
+
+Low resolution or non-standard aspect ratios may be cropped or rejected by LinkedIn.