Skip to content
TrustedSkillsbeta
Back to all skills

Marko Best Practices

Checked
marko-js·vlatest·backend·MIT

Ensures Marko templates adhere to best practices for performance, maintainability, and security using marko-js guidelines.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add marko-js/marko --skill marko-best-practices -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

marko-js

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned marko-js/marko at 70a0594fe2.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
70a0594fe2
Manifest
skills/marko-best-practices/SKILL.md
Scanned
1 file, 31 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides guidance and recommendations for writing effective Marko components. It helps ensure code quality, maintainability, and adherence to best practices within a Marko project. The skill can analyze existing Marko code or provide suggestions during the development process.

When to use it

  • Code review: Use this skill to automatically identify potential issues in Marko component files.
  • Learning Marko: New developers using Marko can leverage this skill for guidance and examples of best practices.
  • Refactoring existing code: Improve the structure and readability of legacy Marko projects.
  • Ensuring consistency: Maintain a consistent coding style across a team working on a Marko application.

Key capabilities

  • Provides recommendations for component structure.
  • Identifies potential performance bottlenecks in Marko components.
  • Offers suggestions for improving code readability and maintainability.
  • Enforces adherence to established Marko best practices.

Example prompts

  • "Analyze this Marko component for potential improvements: [component code]"
  • "What are some best practices for structuring a Marko form?"
  • "Suggest ways to optimize the performance of this Marko list."

Tips & gotchas

This skill assumes familiarity with basic Marko syntax and concepts. While it can identify issues, understanding why certain changes are recommended requires knowledge of Marko's underlying principles.