logs
- Repo stars 330
- License MIT
- Author updated Live
- Author repo claude-skill-registry
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @majiayu000 · MIT
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Shell exec
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: logs
description: View shella daemon and plugin logs. Use when debugging issues, checking what happened, or monito…
category: data
runtime: no special runtime
---
# logs output preview
## PART A: Task fit
- Use case: View shella daemon and plugin logs. Use when debugging issues, checking what happened, or monitoring plugin output. View daemon and plugin logs from ~/.local/state/shella/dev.log. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Arguments / Log File Location / Commands” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “View shella daemon and plugin logs. Use when debugging issues, checking what happened, or monitoring plugin output. View daemon and plugin logs from ~/.local/state/shella/dev.log. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Arguments / Log File Location / Commands” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, run shell commands, write/modify files.
Start with a small task and check whether the result follows “Arguments / Log File Location / Commands”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: logs
description: View shella daemon and plugin logs. Use when debugging issues, checking what happened, or monito…
category: data
source: majiayu000/claude-skill-registry
---
# logs
## When to use
- View shella daemon and plugin logs. Use when debugging issues, checking what happened, or monitoring plugin output. Vi…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Arguments / Log File Location / Commands” and keep inference separate from source facts.
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "logs" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Arguments / Log File Location / Commands
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, run shell commands, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Shella Logs
View daemon and plugin logs from ~/.local/state/shella/dev.log.
Arguments
$ARGUMENTSmay contain:- A plugin name to filter by (e.g., "agent", "terminal")
- A number of lines to show (default: 50)
- "all" to show more lines
- "errors" or "error" to filter to errors/warnings only
Log File Location
~/.local/state/shella/dev.logEach line is JSON with fields: time, level, prefix, msg, and optional data fields.
Commands
Recent logs (last 50 lines):
tail -50 ~/.local/state/shella/dev.logFilter by plugin (prefix field contains plugin name):
grep '"prefix":"agent' ~/.local/state/shella/dev.log | tail -50Errors only:
grep '"level":"error"' ~/.local/state/shella/dev.log | tail -50Parse and format for readability - extract time, prefix, level, msg:
tail -50 ~/.local/state/shella/dev.log | while read line; do
echo "$line" | python3 -c "import sys,json; d=json.loads(sys.stdin.read()); print(f'{d.get(\"prefix\",\"daemon\"):20} {d.get(\"level\",\"info\"):5} {d.get(\"msg\",\"\")}')" 2>/dev/null || echo "$line"
doneOutput
Present logs in a readable format. For JSON lines, extract the key fields (timestamp, prefix, level, message). Highlight errors in your response.
If the log file doesn't exist, tell the user the daemon hasn't been run yet or logs are empty.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review