Deadline

Your personal Deadline assistant. Track, analyze, and manage all your content creation needs from the command line.

Security Scan

The skill's files and runtime instructions are consistent with a local command-line content-tracking tool and do not request unrelated credentials, network access, or elevated persistence.

Purpose & Capability

The name/description (Deadline: local content/deadline manager) match the provided shell script and SKILL.md. The skill only creates/reads files under ~/.local/share/deadline and implements CLI commands that map to the documented functionality. There are no unrelated environment variables, cloud credentials, or unexpected binaries required.

Instruction Scope

SKILL.md and scripts instruct only local operations: logging user inputs, searching local logs, exporting to JSON/CSV/TXT, and simple health checks. The instructions do not direct the agent to read unrelated system files, exfiltrate data, or call external endpoints. The SKILL.md mentions a feedback URL, but the script does not contact it.

Install Mechanism

There is no install spec (instruction-only with an included script). Nothing is downloaded from external URLs and no archives are extracted — this is low-risk from an install perspective. The included script will be written to disk if the skill is installed, which is expected for a CLI helper.

Credentials

The skill declares no required env vars or credentials. At runtime the script uses HOME and standard POSIX utilities (date, mkdir, du, tail, grep, wc, sed, cat), which are reasonable for a local CLI tool. No secrets or unrelated service tokens are requested.

Persistence & Privilege

The skill is not marked always:true and is user-invocable only. It creates and uses a private data directory under the user's home but does not modify other skills, system-wide agent settings, or request permanent elevated privileges.

Assessment

This skill appears to be a straightforward local CLI tool that stores data in ~/.local/share/deadline and does not contact remote services. Before installing: (1) review the included scripts (scripts/script.sh) yourself — the script will be placed on disk; (2) note it uses standard UNIX tools (grep, tail, du, sed, etc.), so run it on systems with those utilities; (3) be aware exports are written as plain text (no escaping), so exported JSON/CSV may be malformed for inputs containing quotes/newlines; and (4) if you prefer extra caution, run the script in a sandbox or inspect/modify it to change the data directory location or tighten escaping/validation.

Your personal Deadline assistant. Track, analyze, and manage all your content creation needs from the command line.

Why Deadline?

• Works entirely offline — your data never leaves your machine
• Simple command-line interface, no GUI needed
• Export to JSON, CSV, or plain text anytime
• Automatic history and activity logging

Getting Started

# See what you can do
deadline help

# Check current status
deadline status

# View your statistics
deadline stats

Commands

Command	What it does
deadline draft	Draft
deadline edit	Edit
deadline optimize	Optimize
deadline schedule	Schedule
deadline hashtags	Hashtags
deadline hooks	Hooks
deadline cta	Cta
deadline rewrite	Rewrite
deadline translate	Translate
deadline tone	Tone
deadline headline	Headline
deadline outline	Outline
deadline stats	Summary statistics
deadline export	<fmt> Export (json
deadline search	<term> Search entries
deadline recent	Recent activity
deadline status	Health check
deadline help	Show this help
deadline version	Show version
deadline $name:	$c entries
deadline Total:	$total entries
deadline Data	size: $(du -sh "$DATA_DIR" 2>/dev/null
deadline Version:	v2.0.0
deadline Data	dir: $DATA_DIR
deadline Entries:	$(cat "$DATA_DIR"/*.log 2>/dev/null
deadline Disk:	$(du -sh "$DATA_DIR" 2>/dev/null
deadline Last:	$(tail -1 "$DATA_DIR/history.log" 2>/dev/null
deadline Status:	OK
deadline [Deadline]	draft: $input
deadline Saved.	Total draft entries: $total
deadline [Deadline]	edit: $input
deadline Saved.	Total edit entries: $total
deadline [Deadline]	optimize: $input
deadline Saved.	Total optimize entries: $total
deadline [Deadline]	schedule: $input
deadline Saved.	Total schedule entries: $total
deadline [Deadline]	hashtags: $input
deadline Saved.	Total hashtags entries: $total
deadline [Deadline]	hooks: $input
deadline Saved.	Total hooks entries: $total
deadline [Deadline]	cta: $input
deadline Saved.	Total cta entries: $total
deadline [Deadline]	rewrite: $input
deadline Saved.	Total rewrite entries: $total
deadline [Deadline]	translate: $input
deadline Saved.	Total translate entries: $total
deadline [Deadline]	tone: $input
deadline Saved.	Total tone entries: $total
deadline [Deadline]	headline: $input
deadline Saved.	Total headline entries: $total
deadline [Deadline]	outline: $input
deadline Saved.	Total outline entries: $total

Data Storage

All data is stored locally at ~/.local/share/deadline/. Each action is logged with timestamps. Use export to back up your data anytime.

Feedback

Found a bug or have a suggestion? Let us know: https://bytesagain.com/feedback/

---

Powered by BytesAgain | bytesagain.com | [e-mail]