Skip to content
Back to skills

Lixrl Links

ASecurity

Manage Lixrl production short links through the installed lixrl CLI. Use when creating, listing, editing, disabling, deleting, exporting, or inspecting analytics for Lixrl links, including links selected for articles or agent-assisted publishing.

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

Works with

  • cli
  • api

Security analysis

A100/100

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

Scanned September 3, 2026

npx -y skills add elixpo/elixpo_chapter --skill lixrl-links --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Lixrl Links?

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

Security grade badge for Lixrl Links
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/elixpo-lixrl-links/badge)](https://www.skillsdirectory.com/skills/elixpo-lixrl-links)

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: lixrl-links
description: Manage Lixrl production short links through the installed lixrl CLI. Use when creating, listing, editing, disabling, deleting, exporting, or inspecting analytics for Lixrl links, including links selected for articles or agent-assisted publishing.
---

# Lixrl Links

Use the installed `lixrl` executable. Do not read credential files or ask the user to paste an API key into chat.

## Workflow

1. Run `lixrl whoami --json --no-input` before authenticated work.
2. If authentication is missing, ask the user to run `lixrl login --open` locally. The user approves identity on the official Elixpo Accounts device page, then chooses the key name, access, and expiry on Lixrl. The CLI stores the resulting key in the OS keychain. Never ask the user to share the one-time code or key in chat.
3. If the user already has a Lixrl key, direct them to `lixrl login --key`; the masked prompt is the only interactive place to paste it.
4. For CI only, use the platform secret store to provide `LIXRL_API_KEY`; never write it to a file, command argument, generated post, or log.
5. Inspect state with `lixrl urls list --json --no-input` before modifying it.
6. Use `--json --no-input` for every automated command.
7. Show the exact target and ask the user before adding `--yes` to delete, revoke, remove, unmap, or overwrite.
8. Report the returned short code or resource ID. Never expose API-key values after key creation.

Run `lixrl --help` for the complete command surface. Prefer `urls disable` over deletion when the desired outcome is reversible.

For articles, release notes, or agent-authored posts, read [references/blog-writing.md](references/blog-writing.md) before creating or replacing links.

Files in this skill

  • SKILL.md1.7 KB
  • agents/openai.yaml212 B
  • references/blog-writing.md1.2 KB

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.