script-manager — community script-manager, Neo-Embedded-Linux, community, ide skills

v1.0.0
GitHub

About this Skill

Ideal for Linux Kernel Driver development agents requiring automated script management on NXP i.MX6ULL Automates the registration and indexing of high-value Python scripts in the projects script library.

yceachan yceachan
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
29
Canonical Locale
en
Detected Body Locale
en

Ideal for Linux Kernel Driver development agents requiring automated script management on NXP i.MX6ULL Automates the registration and indexing of high-value Python scripts in the projects script library.

Core Value

Empowers agents to efficiently manage scripts in the .gemini/scripts/ directory, providing AI-assisted playbooks for saving, creating, or moving high-value scripts, and indexing or registering scripts on demand, utilizing trigger conditions for active, passive, and negative script handling

Ideal Agent Persona

Ideal for Linux Kernel Driver development agents requiring automated script management on NXP i.MX6ULL

↓ Capabilities Granted for script-manager

Automating script registration for permanent scripts
Indexing high-value scripts in .gemini/scripts/
Managing script workflows for Linux Kernel Driver development on NXP i.MX6ULL

! Prerequisites & Limits

  • Requires access to .gemini/scripts/ directory
  • Limited to Linux Kernel Driver development on NXP i.MX6ULL
  • Excludes temporary or throwaway scripts unless explicitly requested

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is script-manager?

Ideal for Linux Kernel Driver development agents requiring automated script management on NXP i.MX6ULL Automates the registration and indexing of high-value Python scripts in the projects script library.

How do I install script-manager?

Run the command: npx killer-skills add yceachan/Neo-Embedded-Linux. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for script-manager?

Key use cases include: Automating script registration for permanent scripts, Indexing high-value scripts in .gemini/scripts/, Managing script workflows for Linux Kernel Driver development on NXP i.MX6ULL.

Which IDEs are compatible with script-manager?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for script-manager?

Requires access to .gemini/scripts/ directory. Limited to Linux Kernel Driver development on NXP i.MX6ULL. Excludes temporary or throwaway scripts unless explicitly requested.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add yceachan/Neo-Embedded-Linux. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use script-manager immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

script-manager

Install script-manager, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Script Manager Skill

1. Trigger Conditions (When to use)

  • Active: When the Agent saves, creates, or moves a "permanent" or "high-value" script into .gemini/scripts/.
  • Passive: When the user explicitly asks to "index scripts" or "register this script".
  • Negative: Do not trigger for temporary, throwaway, or one-off debugging scripts unless explicitly requested.

2. Core Workflow

  1. Identify: Confirm the script is located in (or being written to) .gemini/scripts/.
  2. Validate: Ensure the script has a docstring describing its purpose.
  3. Register: Update .gemini/scripts/GEMINI.md.
    • If the file doesn't exist, create it.
    • Add a row to the "Registered Scripts" table.

3. Index Format (.gemini/scripts/GEMINI.md)

The index file must contain a table with the following columns:

Script NameFunctionUsage ExampleTags
example_script.pyBrief description of what it does.python .gemini/scripts/example.py --argpdf, extraction

4. Instructions for Agent

  • Consistency: Always check existing tags and try to reuse them (e.g., pdf, parsing, validation).
  • Brevity: Keep descriptions under 15 words.
  • Verification: After updating the index, verify the entry is correct.

Related Skills

Looking for an alternative to script-manager or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer