Skills os-scripting
๐Ÿ“ฆ

os-scripting

Content revision r2 Safe โš™๏ธ External commands๐ŸŒ Network access๐Ÿ“ Filesystem access

Troubleshoot and Automate Operating Systems

Shell troubleshooting often becomes inconsistent across diagnosis, repair, testing, and automation. This skill provides a structured workflow for Bash analysis, Linux diagnostics, testing, and scheduled operations.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "os-scripting" from https://skillstore.io/skills/sickn33-os-scripting.md and its manifest at https://skillstore.io/api/skills/sickn33-os-scripting/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Test it

Using "os-scripting". A backup script exits early when an optional directory is absent.

Expected outcome:

  • Likely cause: strict error handling treats the missing optional path as fatal.
  • Recommended change: validate optional paths and handle absence explicitly.
  • Validation: run ShellCheck and test present, absent, and inaccessible directory cases.

Using "os-scripting". A Linux service consumes high CPU after deployment.

Expected outcome:

  • Start with process and service status evidence, then compare recent logs.
  • Confirm the affected process before tracing or restarting it.
  • Record a rollback condition and monitor CPU after the approved change.

Using "os-scripting". Create a daily maintenance workflow for log cleanup.

Expected outcome:

The plan includes retention rules, a tested cleanup script, approval before scheduling, failure logging, disk monitoring, and a rollback procedure.

Security Audit

Safe
v6 โ€ข 8/4/2026 Open versioned report

All 88 static findings are false positives caused by Markdown formatting or transparent operating system administration examples. No prompt injection, hidden execution, credential access, data exfiltration, or malicious persistence intent was found.

1
Files scanned
434
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-os-scripting/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-os-scripting/security.svg)](https://skillstore.io/skills/sickn33-os-scripting?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-os-scripting?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-os-scripting/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-os-scripting.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

sickn33. (2026). os-scripting security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-os-scripting/audits/6

BibTeX citation

@techreport{sickn33-sickn33-os-scripting-2026, author = {sickn33}, title = {os-scripting security audit report (audit version 6)}, institution = {Skillstore}, year = {2026}, number = {6}, url = {https://skillstore.io/skills/sickn33-os-scripting/audits/6}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "os-scripting security audit report (audit version 6)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-08-04" url: "https://skillstore.io/skills/sickn33-os-scripting/audits/6" identifiers: - type: other value: "skillstore:sickn33-os-scripting:audit:6" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
68
Community
83
Spec Compliance

What You Can Build

Repair a failing shell script

Trace errors, apply defensive Bash patterns, and define focused regression tests.

Diagnose a Linux service incident

Collect system evidence, rank likely causes, and prepare controlled recovery steps.

Plan recurring maintenance

Design a tested script, scheduling approach, monitoring checks, and rollback procedure.

Try These Prompts

Assess a system issue
Assess this system issue: [SYMPTOMS]. Identify the operating system, collect read-only diagnostics, explain findings, and request approval before any change.
Review a Bash script
Review [SCRIPT] for quoting, error handling, portability, and unsafe assumptions. Explain each issue, propose revisions, and outline ShellCheck validation.
Design shell tests
Design Bats tests for [SCRIPT] covering success, missing arguments, edge cases, and failures. Describe fixtures, isolation, expected results, and cleanup.
Investigate and automate recovery
Investigate [INCIDENT] on [ENVIRONMENT]. Build a phased diagnostic plan, rank hypotheses, minimize privilege, define rollback steps, and propose monitored automation.

Best Practices

  • Begin with read-only diagnostics and record the current state before making changes.
  • Validate scripts with ShellCheck and focused tests before deployment or scheduling.
  • Request explicit approval for privileged commands, service changes, and persistent automation.

Avoid

  • Do not run broad root-level searches before confirming scope and resource impact.
  • Do not restart services or edit schedules without validation and rollback steps.
  • Do not paste untrusted values into shell commands without quoting and input validation.

Frequently Asked Questions

Which operating systems does this skill cover?
The workflow mentions Linux, macOS, and Windows, but most concrete commands and templates are for Linux and Bash.
Does the skill execute commands automatically?
No executable files are included. An agent may run suggested commands only when the environment and user permissions allow it.
Can it create production-ready Bash scripts?
It provides a defensive structure and quality checklist. Production use still requires environment-specific review, tests, and deployment controls.
Does it support shell script testing?
Yes. It outlines ShellCheck analysis and Bats tests for success, failures, arguments, edge cases, and output files.
Can it configure cron or systemd timers?
It can plan schedules and show examples. Persistent changes require explicit approval, correct permissions, monitoring, and rollback preparation.
Are the diagnostic commands always safe?
No. Some commands require privileges, scan broad paths, expose system details, consume resources, or alter services and schedules.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

81e05e636292629114b76cbb3922fbe57672fc02

Maintenance freshness

8/5/2026

Usage

13 downloads ยท 93 views

File structure

๐Ÿ“„ SKILL.md