New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Verify Persistence

by hmislk in hmislk/hmis

Verify persistence.xml configuration before git push. An agent skill from hmislk/hmis.

GPL-3.0Auto-check: notesDevOps & Cloud

Install Verify Persistence

skills CLI
$ npx skills add hmislk/hmis --skill verify-persistence -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hmislk/hmis verify-persistence --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hmislk/hmis.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/verify-persistence .claude/skills/verify-persistence && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
verify-persistence
GitHub stars
236
Token cost
~368 tokens
SKILL.md length
116 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
GPL-3.0

At a glance

Verify persistence.xml configuration before git push. An agent skill from hmislk/hmis.

  • Works in 4 steps: Read persistence.xml at… → Check JNDI datasources - Must use… → Check DDL generation paths - Must NOT… → …
  • Tasks that involve Secrets management
  • SKILL.md covers Steps, What's Correct vs Wrong and If Issues Found
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Verify Persistence is an agent skill from hmislk/hmis. Verify persistence.xml configuration before git push. Use before pushing code to ensure persistence.xml uses environment variables instead of hardcoded JNDI names. Prevents QA deployment failures.

Its SKILL.md is about 370 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Secrets management. It works with Git. The repository describes itself as: This is an Open Source Java EE based Hospital Information Management System. The licence is GPL-3.0.

When your agent uses it

  • Tasks that involve Secrets management

Example prompts

  • “/verify-persistence”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Bash

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read persistence.xml at src/main/resources/META-INF/persistence.xml
  2. Check JNDI datasources - Must use environment variables
  3. Check DDL generation paths - Must NOT contain hardcoded paths
  4. Report findings clearly

What it can do on your machine

Read from SKILL.md and the folder at commit d5d2020. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verify Persistence loads about 368 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 116 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~368

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hmislk/hmis at commit d5d2020, republished under its GPL-3.0 licence (© hmislk). 116 words, ~368 tokens.

Download SKILL.mdSave it as .claude/skills/verify-persistence/SKILL.md (or your agent's skills folder).
name
verify-persistence
description
Verify persistence.xml configuration before git push. Use before pushing code to ensure persistence.xml uses environment variables instead of hardcoded JNDI names. Prevents QA deployment failures.
allowed-tools
Read, Grep, Bash
disable-model-invocation
true

Verify Persistence Configuration

Check src/main/resources/META-INF/persistence.xml for deployment readiness.

Steps

  1. Read persistence.xml at src/main/resources/META-INF/persistence.xml

  2. Check JNDI datasources - Must use environment variables:

    • ${JDBC_DATASOURCE} (not jdbc/coop, jdbc/rhDS, etc.)
    • ${JDBC_AUDIT_DATASOURCE} (not jdbc/ruhunuAudit, etc.)

  3. Check DDL generation paths - Must NOT contain hardcoded paths:

    • No eclipselink.application-location with c:/tmp/ or /home/*/tmp/

  4. Report findings clearly:

    • If all correct: "Persistence.xml is deployment-ready"
    • If issues found: List each issue with the current value and what it should be

What's Correct vs Wrong

SettingCorrectWrong
Main datasource${JDBC_DATASOURCE}jdbc/coop, jdbc/rhDS
Audit datasource${JDBC_AUDIT_DATASOURCE}jdbc/ruhunuAudit
DDL locationNot present or env varc:/tmp/, /home/buddhika/tmp/

If Issues Found

Offer to fix by replacing hardcoded values with environment variables. Do NOT auto-fix without user confirmation.

© hmislk, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .codex/skills/verify-persistence of hmislk/hmis.

Open the folder on GitHubat commit d5d2020

Compare with similar skills

Verify Persistence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Verify Persistence compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify Persistence this skillhmislk/hmis236—~368Automated safety check: NotesGPL-3.0
Secrets GitleaksAgentSecOps/SecOpsAgentKit2202 repos~4.1kAutomated safety check: PassCustom licence
Network Proxydidi/mpx3.9k—~464Automated safety check: PassApache-2.0
Private Secret Scanningjamditis/claude-skills-journalism416—~1.8kAutomated safety check: PassMIT
KubeSphere DevOps Credentialskubesphere/kubesphere17k—~4.2kAutomated safety check: PassCustom licence
Dotenvx Secretskortix-ai/suna20k—~4.2kAutomated safety check: NotesCustom licence

Similar skills

  • Secrets Gitleaks

    AgentSecOps/SecOpsAgentKit

    Hardcoded secret detection and prevention in git repositories and codebases using Gitleaks.

    220 GitHub starsUsed in 2 repos~4.1k tokens
    DevOps & CloudAuto-check passed

  • Network Proxy

    didi/mpx

    Helps when network-related commands (like curl, git, npm, pip, brew) are failing, timing out, or running slowly due to network issues.

    3.9k GitHub stars~464 tokensUpdated today
    DevOps & CloudAuto-check passed

  • Private Secret Scanning

    jamditis/claude-skills-journalism

    Local Gitleaks scans for staged changes, push ranges, and full history in private repos, with redacted reports.

    416 GitHub stars~1.8k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed

  • KubeSphere DevOps Credentials

    kubesphere/kubesphere

    Covers creating and managing KubeSphere DevOps credentials as typed Kubernetes Secrets that sync to Jenkins, including the API endpoints and a common pitfall.

    17k GitHub stars~4.2k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

  • Dotenvx Secrets

    kortix-ai/suna

    How this repo manages API secrets and the four local-run environments (local/dev/staging/prod).

    20k GitHub stars~4.2k tokensUpdated today
    DevOps & CloudAuto-check: notes

  • Implementing Secret Scanning With Gitleaks

    mukul975/Anthropic-Cybersecurity-Skills

    This skill covers implementing Gitleaks for detecting and preventing hardcoded secrets in git repositories.

    34k GitHub stars~2.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

More from hmislk/hmis

All 33 skills in this repo

  • API Usage

    hmislk/hmis

    Reference for calling existing HMIS REST APIs. An agent skill from hmislk/hmis.

    236 GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • App Configuration

    hmislk/hmis

    Application configuration options reference for the HMIS project.

    236 GitHub stars~474 tokensUpdated today
    Auto-check passed

  • Caveman

    hmislk/hmis

    Ultra-compressed communication mode. An agent skill from hmislk/hmis.

    236 GitHub starsUsed in 21 repos~946 tokens
    Auto-check passed

  • Database Guide

    hmislk/hmis

    MySQL database development guide for the HMIS project. An agent skill from hmislk/hmis.

    236 GitHub stars~664 tokensUpdated today
    Auto-check passed

  • Demo Video

    hmislk/hmis

    A skill your agent uses when asked to make a demo, training, how-to or tutorial video with sound or voice-over showing an HMIS function or configuration (e.g.

    236 GitHub stars~3.9k tokensUpdated today
    Auto-check passed

  • Deploy QA

    hmislk/hmis

    Sync development into QA/testing environment branches (QA1-QA4, local RH staging) via PR + merge on GitHub.

    236 GitHub stars~2.1k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Verify Persistence

What does Verify Persistence do?

Verify persistence.xml configuration before git push. An agent skill from hmislk/hmis. Verify Persistence is an agent skill from hmislk/hmis.xml configuration before git push.

When should I use Verify Persistence?

Verify Persistence fits situations like: tasks that involve Secrets management.

How do I install Verify Persistence in Claude Code?

Run `npx skills add hmislk/hmis --skill verify-persistence -a claude-code`. Or copy the skill folder (.codex/skills/verify-persistence in hmislk/hmis) into .claude/skills/verify-persistence in your project. Claude Code loads it when a task matches its description.

How do I install Verify Persistence in Codex?

Run `npx skills add hmislk/hmis --skill verify-persistence -a codex`. Or copy the skill folder (.codex/skills/verify-persistence in hmislk/hmis) into .agents/skills/verify-persistence in your project. Codex loads it when a task matches its description.

Can I use Verify Persistence in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hmislk/hmis --skill verify-persistence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-persistence, .gemini/skills/verify-persistence, .github/skills/verify-persistence and .opencode/skills/verify-persistence in your project.

What does Verify Persistence need to run?

SKILL.md names no scripts, command-line tools or credentials: Verify Persistence is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Bash.

Does Verify Persistence access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Verify Persistence safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Verify Persistence use?

Verify Persistence is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify Persistence use?

About 368 tokens (SKILL.md is roughly 1.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Verify Persistence?

Skills that share tags, products or a category with Verify Persistence: Secrets Gitleaks (AgentSecOps/SecOpsAgentKit, 220 stars), Network Proxy (didi/mpx, 3.9k stars), Private Secret Scanning (jamditis/claude-skills-journalism, 416 stars) and KubeSphere DevOps Credentials (kubesphere/kubesphere, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify Persistence?

hmislk (a GitHub organization) maintains it in hmislk/hmis, which has 236 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 8, 2026.

Source: hmislk/hmis on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.