Use this skill automatically when you feel your code is ready for human review, and whenever writing or reviewing code comments. Ready means the code works and achieves a stated goal, verified by your own tests and/or, if you deem it necessary, human testing.
justfiles/justfiles
Score58
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Improve a Hinge dating profile through research-backed screenshot audits, photo selection and ordering, conversational discovery, prompt and caption writing, settings review, or post-launch troubleshooting. Use for a full profile rebuild or a focused request about photos, copy, positioning, match quality, or profile performance.
Correct, revise, or rebuild an existing PPTX or Clara HTML deck from spoken feedback, a call transcript, screen recording, review notes, or partner comments. Use when the user says record feedback on this deck or when the requested outcome is a changed deck rather than only a transcript: open Clara Voice Capture when needed, interpret every requested change, preserve untouched content, require a reviewable understanding and approval checkpoint for PPTX work, apply changes to a copy, render, verify, and inspect the final audience-facing deck. Do not use for transcription alone or for creating a new deck without revision feedback.
Bundle TypeScript and JavaScript libraries with blazing-fast speed powered by Rolldown. Use when building libraries, generating type declarations, bundling for multiple formats, or migrating from tsup.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Create or update the skill registry for the current project. Scans user skills and project conventions, writes .atl/skill-registry.md, and saves to engram if available. Trigger: When user says "update skills", "skill registry", "actualizar skills", "update registry", or after installing/removing skills.
Manage Telegram channel access — approve pairings, edit allowlists, set DM/group policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Telegram channel.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?"
Shape an unclear feature or design with the user before any plan exists — one question at a time, 2-3 approaches, and a local browser companion for mockups and diagrams. Use when the user says "brainstorm", "explore this idea", "show me options", or asks for something whose intent or design is still open. Skip it when the task is already specified.
Generate a concise tech-stack decision doc (chosen stack + rejected alternatives, tabular) for a project. Use when the user asks to document/write/create a tech stack, stack decision doc, or "tech-stack.md".
Use before and after changing code in a git repo: collects the change's impact list (what it can break, and what new behavior must fit), checks it against the per-repo behavior map with ,behavior-map, maps unmapped areas, and maintains entries (area init, update, add, refresh, promote, resolve).
Authors, reviews, and diagnoses Task (go-task) automation in Taskfile.yml, Taskfile.yaml, included Taskfiles, and .taskrc.yml. Use for ordered or parallel workflows, typed inputs and CLI arguments, stale builds, reusable monorepo tasks, watch/CI failures, or remote Taskfile trust.
Create safe targeted refactoring plans. Use when asked to plan simplification, cleanup, extraction, renaming, deletion, or module movement without applying changes. For small in-place fixes, use `code-cleanup` instead.
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.
Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill", or wanting agents to follow how the user works. Drafts or revises a personal -mode skill via create-skill + unslop, optionally pulling fresh evidence from recent transcripts.
The Diamond Model of Intrusion Analysis provides a structured framework for analyzing cyber intrusions by examining four core features - Adversary, Capability, Infrastructure, and Victim. This skill covers implementing the Diamond Model programmatically to classify and correlate intrusion events, build activity threads, and generate pivot-ready intelligence.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.
Review the upstream source before running this command.
How is this score calculated?
Weighted across six dimensions, scored 0-100.
Provenance (25): listed in an official or curated registry.
Installability (25): a runnable install command beats a declared transport, which beats a source checkout.
Maintenance (20): recency of the last push; archived entries score zero here.
Adoption (20): repository stars on a log curve.
Documentation (10) and description quality (10): parsed manifest or SKILL.md frontmatter, and a real description rather than a placeholder.
Dimensions a source cannot supply — registries publish no stars or license — are excluded from the entry's own average instead of counted as zero, so entries stay comparable across sources.
Security signals subtract up to 20. Scores are recomputed on every daily ingest.