Paid-course example showing how to package a self-contained Logion bundle with the marketplace paid license. Use as a starting point when you want a benign course that reads local artifacts, produces a structured report, and exercises the paid publication path end to end.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add nicolasmelo1/logion --skill with-paid --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of With Paid?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nicolasmelo1-with-paid)More formats (shields.io, HTML) on the badges page.
---
name: with-paid
description: Paid-course example showing how to package a self-contained Logion bundle with the marketplace paid license. Use as a starting point when you want a benign course that reads local artifacts, produces a structured report, and exercises the paid publication path end to end.
version: 1.0.0
author: logion-examples
license: Logion Standard Course License v1.0
platforms: [linux]
compatibility: Requires python3 on the host.
metadata:
hermes:
tags: [reporting, audit, paid-course]
category: operations
related_skills:
- minimal
- with-references-and-scripts
---
# With-Paid Skill
This is a benign paid-course example. It exists to demonstrate the paid bundle
contract: self-contained files, explicit capabilities, and the Logion Standard
Course License v1.0.
## When to Use
- You want a reference paid bundle to test create -> upload -> complete.
- You need a simple course that reads local notes and writes a structured
report.
- You want an example that exercises the paid-license enforcement path without
introducing risky operational content.
## Prerequisites
- `file` and `terminal` tools.
- `python3` available on the host.
## How to Run
```bash
python3 scripts/render_report.py ./inputs/findings.txt ./outputs/report.md
```
## Output
The script reads a plain-text findings list and writes a normalized markdown
report under `outputs/`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.