performance-memory-catalyst

Ensures the app runs efficiently and safely by handling memory management, state architecture, and Coroutine optimizations. Use this skill to fix memory leaks (OOM), optimize Coroutine dispatchers, enforce immutable StateFlow architectures, add database indexes, or resolve Compose state bottlenecks.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/catalyst/SKILL.md

Quality

Content

75%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.

A well-structured, concise instruction skill with a clear sequenced workflow and concrete, actionable guidance for Android performance work. Main weakness is the absence of a tight validate→fix→retry error-recovery loop and any runnable code examples.

Suggestions

Add an explicit feedback loop in VERIFY, e.g. 'If tests fail or ktfmtFormat reports issues, fix and re-run until both pass before presenting the PR.'

Include one short executable Kotlin snippet illustrating a representative optimization (e.g. wrapping a Cursor in .use{} or adding @Index) to lift actionability to copy-paste ready.

Tighten the journaling-rules paragraph or move the detailed format spec into the referenced .jules/catalyst.md file to trim tokens from the main body.

Dimension	Reasoning	Score
Conciseness	Lean and punchy with no concept-explanation padding ('If you open it, close it'), though the journaling-rules and philosophy blocks add minor verbosity.	4 / 5
Actionability	Concrete commands (./gradlew ktfmtFormat, lintDebug) and specific patterns (.use{}, @Index, @Immutable, distinctUntilChanged) guide execution, but instruction-style guidance lacks runnable copy-paste code blocks.	4 / 5
Workflow Clarity	A clear 5-step PROFILE→PRESENT sequence with explicit validation (VERIFY runs tests, checks for race conditions/NPEs) and an approval gate, but the validate→fix→retry feedback loop is implicit rather than spelled out.	4 / 5
Progressive Disclosure	Well-organized single-file skill with clear sections (Goal, Constraints, Instructions, Examples) and no bundle files needed; slightly exceeds the simple-skill line and references an inline .jules/catalyst.md journal file.	4 / 5
	Total	16 / 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, specific description that names concrete capabilities and provides an explicit 'Use this skill to...' trigger clause with natural terms. It is comprehensive for its niche with only minor keyword-coverage gaps.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('fix memory leaks (OOM), optimize Coroutine dispatchers, enforce immutable StateFlow architectures, add database indexes') with only minor coverage gaps.	4 / 5
Completeness	Explicitly answers what ('handling memory management, state architecture, and Coroutine optimizations') and when ('Use this skill to fix...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural Android-dev terms like 'memory leaks (OOM)', 'Coroutine dispatchers', 'Compose state bottlenecks' are present, though a few common synonyms (Flow, Room, recomposition) are missing.	4 / 5
Distinctiveness Conflict Risk	Clear Android performance/memory niche with distinct triggers and minimal conflict risk, with only slight potential overlap against a general Android skill.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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: nekomangaorg/Neko
Path: .agents/skills/catalyst/SKILL.md
Commit: 9852a3f

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.