CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nex-life-logger

Logs browser history, active windows and watched videos locally, then lets your agent answer questions about what you were doing. Use when: Reconstruct workdays for accurate billing and timesheets; Find forgotten websites or videos using natural language search; Analyze weekly productivity patterns and time distribution.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/nex-business-operations/skills/nex-life-logger/SKILL.md

The canonical home for this skill is nex-life-logger in NexaiGuy/nex-ai-skills

SKILL.md
Quality
Evals
Security

Quality

Content

22%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body reads as a product landing page rather than an agent skill: it is well organized and honest about limitations, but it contains zero executable instructions, commands, or workflows, and explicitly admits the scripts and templates that would make it work are missing from the folder. An agent reading this could not perform the skill's function.

Suggestions

Add an actionable usage section showing the actual query/search command syntax with executable examples (e.g., how to filter by date, activity type, or browser), instead of only describing that 'it provides a search command with filters'.

Include setup/invocation steps (installation, starting the logger, connecting the query layer) as a sequenced workflow, and either bundle the referenced scripts/templates in the skill folder or remove claims about them.

Trim promotional content ('Free skill by Nex AI', the paid-catalog link, the privacy-respecting-alternative pitch) so every remaining token contributes to instructing the agent.

DimensionReasoningScore

Conciseness

The body is short and sectioned without explaining concepts Claude already knows, but it carries padding that earns no tokens: 'Free skill by Nex AI', 'A privacy-respecting alternative to cloud time trackers', and the footer 'More skills, including the paid catalog: https://www.agensi.io/...'. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened'; it is not the lean, every-token-earns-its-place level 5.

3 / 5

Actionability

There is no executable guidance anywhere: no commands, no code, no invocation syntax, no setup steps. It only describes capability ('Exposes a query layer', 'it provides a search command with filters') without ever showing that command, and even states 'Scripts, extension source, and templates from the original package are not in this folder'. This is the 'only describes rather than instructs' anchor — it does not reach level 2, which requires at least high-level how-to hints.

1 / 5

Workflow Clarity

No sequence of steps exists — not even a rough one — for installing, configuring, or querying the logger; the 'Example' section shows a request and its answer with no indication of how to produce it. This matches 'steps missing or incoherent; no sequence' rather than level 2, which requires a rough but present sequence.

1 / 5

Progressive Disclosure

The body is under 50 lines with clear sections (What it does, Use cases, Limitations, Example, Questions), but the material that would make the skill usable — scripts, extension source, templates — is declared absent ('not in this folder') with no in-repo pointers or file listing, and no references/ or scripts/ directories exist. Structure is present but the actual detailed content is neither inline nor referenced, fitting 'some structure but could be better organized' rather than the well-split level 4/5.

3 / 5

Total

8

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concrete about data sources and the query capability, with an explicit 'Use when:' clause listing three realistic trigger scenarios. Keyword coverage is good though it misses common synonyms like 'time tracking' or 'activity tracker', and the summarization capability from the body is not surfaced here.

DimensionReasoningScore

Specificity

Quotes several concrete actions — 'Logs browser history, active windows and watched videos locally' plus a query layer ('lets your agent answer questions about what you were doing') — which matches the 'several specific actions; minor gaps' anchor. It falls short of 5 because capabilities like time summarization per project/application and the search filters (mentioned only in the body) are absent from the description.

4 / 5

Completeness

It explicitly answers both parts: the 'what' ('Logs browser history, active windows and watched videos locally, then lets your agent answer questions') and an explicit 'Use when:' clause with three concrete trigger scenarios (billing/timesheets, finding forgotten sites, productivity analysis). This matches the anchor for clearly and explicitly answering both with concrete trigger phrases; the 4 anchor applies only when 'when' is less explicit.

5 / 5

Trigger Term Quality

Natural phrases users would say are well covered: 'browser history', 'billing and timesheets', 'forgotten websites or videos', 'natural language search', 'productivity patterns'. Missing common synonyms such as 'time tracking', 'screen time', 'activity tracker', or 'watch history', so it fits the 'good keyword coverage; a few natural terms missing' anchor rather than 5.

4 / 5

Distinctiveness Conflict Risk

The local life-logging niche ('browser history, active windows, watched videos', workday reconstruction) is mostly distinct with clear triggers. Minor overlap risk remains with general time-tracking/productivity-analysis skills (e.g., 'Analyze weekly productivity patterns'), keeping it at 'mostly distinct; minor overlap risk' rather than the minimal-conflict 5 anchor.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

NexaiGuy/nex-ai-skills

Path

plugins/nex-business-operations/skills/nex-life-logger/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.