CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mamba-architecture

State-space model with O(n) complexity vs Transformers' O(n²). 5× faster inference, million-token sequences, no KV cache. Selective SSM with hardware-aware design. Mamba-1 (d_state=16) and Mamba-2 (d_state=128, multi-head). Models 130M-2.8B on HuggingFace.

56

Quality

70%

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 ./backend/cli/skills/ml-training/mamba/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 is highly actionable with complete, runnable code and concrete troubleshooting, but it is self-contained to a fault: none of the three bundled reference files are referenced anywhere, so their detail is unreachable, and performance claims are restated across four sections. Linking the reference files and deduplicating the performance block would resolve the weakest dimensions.

Suggestions

Add a references section linking the bundled files, e.g. '**Architecture details**: See [references/architecture-details.md](references/architecture-details.md)' for architecture-details, benchmarks, and training-guide, so the bundle content is discoverable.

Consolidate the repeated performance claims (5× faster, no KV cache, linear scaling) into one section and delete the duplicates from Workflow 4, Advantages, Hardware requirements, and Performance.

Remove the empty 'Advanced topics' heading (fold Hardware requirements under it or drop the heading), and clarify where benchmarks/benchmark_generation_mamba_simple.py comes from (upstream repo vs. bundle).

DimensionReasoningScore

Conciseness

Mostly efficient code-first sections, but "5× faster inference" is repeated in four places (Workflow 4 expected results, Advantages, Hardware requirements, and the Performance block, which also repeats "No KV cache" and "Linear vs quadratic"), and the "Advanced topics" heading is empty with its content just being hardware requirements. Not 4 because this redundancy is more than minor and the version pins ("PyTorch 1.12+, CUDA 11.6+") sit outside any deprecation section.

3 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: install commands ("pip install mamba-ssm[causal-conv1d]"), complete runnable code blocks with real parameter values, named HuggingFace checkpoints ("state-spaces/mamba-2.8b"), and concrete issue fixes ("pip install mamba-ssm --no-build-isolation"). Covers the common cases (build LM, load pretrained, compare Mamba-1/2, benchmark).

5 / 5

Workflow Clarity

The four workflows are unambiguous and the Common issues section provides error-to-fix loops ("Reduce batch size or use gradient_checkpointing_enable()", "Use MambaLMHeadModel.from_pretrained (not AutoModel)"). Not 5 because workflows lack explicit validation checkpoints and the benchmark command references "benchmarks/benchmark_generation_mamba_simple.py" without stating where that script comes from; not 3 because sequences are complete and error recovery is present for the common failure modes.

4 / 5

Progressive Disclosure

The bundle provides references/architecture-details.md, references/benchmarks.md, and references/training-guide.md, but the body never links to or mentions any of them — they are orphaned and undiscoverable — while inline sections (benchmark expectations, Mamba-1 vs Mamba-2 key differences, hardware requirements) duplicate material that belongs in those files. This matches 'content that clearly belongs in separate files is inlined; references are buried'. Not 3 because structure alone does not offset the complete absence of signaled navigation to the existing reference files.

2 / 5

Total

14

/

20

Passed

Description

61%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 dense, factual description that clearly conveys the skill's niche and technical specifics, but it is a spec-sheet of architecture properties rather than a statement of capabilities, and it lacks any 'use when' trigger guidance. Adding an explicit trigger clause and one or two capability verbs would lift the two capped dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with Mamba, state-space models, or replacing Transformers for long-context/efficient-inference workloads.'

Lead with capability verbs (train, fine-tune, load, benchmark) so the description states what the skill does, not just what Mamba is.

Include common synonyms such as 'sequence modeling', 'long context', and 'linear attention' to broaden natural trigger-term coverage.

DimensionReasoningScore

Specificity

The description states concrete technical facts ("Selective SSM with hardware-aware design", "Mamba-1 (d_state=16) and Mamba-2 (d_state=128, multi-head)", "Models 130M-2.8B on HuggingFace") but these are properties of the architecture rather than actions the skill performs, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. Not 4 because no list of specific actions (train, load, benchmark, compare) is given.

3 / 5

Completeness

The 'what' is clear (a Mamba state-space model architecture skill with concrete model details), but there is no 'Use when...' clause or equivalent explicit trigger guidance — "Use Mamba when" appears only in the body, not the description — which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' is concrete and specific rather than vague.

3 / 5

Trigger Term Quality

Good natural keyword coverage — "State-space model", "Mamba-1", "Mamba-2", "SSM", "Transformers", "inference", "HuggingFace" — terms users would actually say when needing this skill. Not 5 because common variations like "sequence modeling", "linear attention", or "long context" as a phrase are missing.

4 / 5

Distinctiveness Conflict Risk

Mamba/SSM is a clear niche and the description explicitly positions against "Transformers' O(n²)", making it mostly distinct. Not 5 because generic ML terms ("inference", "HuggingFace", "Transformers") give minor overlap risk with adjacent ML-training skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

synthetic-sciences/openscience

Path

backend/cli/skills/ml-training/mamba/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.