Skip to content
Back to skills

Lixblogs Organizations

ASecurity

Inspect LixBlogs organization memberships, roles, collections, and valid publication targets through the supported CLI. Use when an agent must choose or verify a personal, organization, or collection target without crossing tenant boundaries.

  • 85 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 3, 2026
devopsbash

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 3, 2026

npx -y skills add elixpo/elixpo_chapter --skill lixblogs-organizations --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lixblogs Organizations?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Lixblogs Organizations
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/elixpo-lixblogs-organizations/badge)](https://www.skillsdirectory.com/skills/elixpo-lixblogs-organizations)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: lixblogs-organizations
description: Inspect LixBlogs organization memberships, roles, collections, and valid publication targets through the supported CLI. Use when an agent must choose or verify a personal, organization, or collection target without crossing tenant boundaries.
---

# LixBlogs organizations

Use `@elixpo/lixblogs-cli` 1.2.0 or newer and add `--json --no-input` for automation. Use only CLI commands; never access D1, cookies, passwords, tokens, or endpoints directly.

## Access

This read-only workflow requires `lixblogs:organizations:read`. It does not authorize organization changes or publication. Verify the active identity and scope first:

```bash
lixblogs whoami --json --no-input
lixblogs org list --json --no-input
```

## Resolve a target

1. Use `org list` to obtain authenticated memberships and effective roles.
2. Use the returned organization ID—not an unverified slug—to inspect it.
3. Use `org targets` for writable publication targets. It excludes read-only memberships.
4. If a collection is requested, select its ID only from the target's returned collection list.
5. Present the chosen tenant, role, and collection to the user before passing `--publication org:ORG_ID` or `--collection COLLECTION_ID` to an authoring command.

```bash
lixblogs org get ORG_ID --json --no-input
lixblogs org collections ORG_ID --json --no-input
lixblogs org members ORG_ID --json --no-input
lixblogs org targets --json --no-input
```

Roles `admin`, `maintain`, and `write` may appear as writable. `read` is inspection-only. Never infer access from a public organization page, a slug, a previous run, or user-supplied metadata; the current CLI response is authoritative.

## Safety and recovery

- `org_not_found` also represents inaccessible tenants. Do not probe alternate identifiers.
- `insufficient_scope`: request only `lixblogs:organizations:read`.
- A missing target means the current identity cannot publish there; stop instead of falling back to a similarly named organization.
- Re-run `org targets` immediately before a draft changes publication tenant because memberships and roles can change.
- Report request IDs for diagnosis without printing credentials.

Use `lixblogs-author` to draft after target selection and `lixblogs-publish` for a separately approved public-state change.

Files in this skill

  • SKILL.md2.3 KB
  • agents/openai.yaml295 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.