CtrlK
BlogDocsLog inGet started
Tessl Logo

dev-environment

Reference for the OrangeHRM Docker-based local development environment — container layout, hostnames, common docker compose commands, how to shell into PHP containers, how to access the DB, and the LOCAL_SRC mounting convention. Use whenever the user asks about running OrangeHRM locally, which PHP version to use (lowest supported), switching PHP versions, accessing the app over HTTP or HTTPS (ports 80/443), accessing the dev database, rebuilding containers, or anything involving the `orangehrm-os-dev-environment` repo. Also covers troubleshooting a broken dev environment — containers that won't start or keep crashing, image build failures, the app being unreachable at `http://phpXX/`, host port 80/443 conflicts ("port is already allocated" / "address already in use"), "database connection refused", and mount/`LOCAL_SRC` problems — and checking this reference against the `orangehrm-os-dev-environment` companion repo for drift (renamed services, changed PHP/DB matrix, new ports or `.env` keys).

72

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured dev-environment reference with strong diagnostic workflows, but it is long and somewhat repetitive and keeps all reference material inline rather than splitting it into bundle files.

Suggestions

Tighten repeated safety admonitions (e.g. 'never edit the OrangeHRM tree') into a single stated rule referenced where needed, to reduce token cost.

Move the available-services PHP/DB matrix and the troubleshooting table into a references/ file and link to them from SKILL.md to improve progressive disclosure.

Condense the memory-recording advisory block to a short example plus a one-line instruction rather than multiple paragraphs of justification.

DimensionReasoningScore

Conciseness

The body is information-dense with no beginner-concept padding, but at ~200 lines it repeats admonitions ('never edit the OrangeHRM tree' appears several times) and includes wordy advisory prose (the memory-recording block, 'developer's call' framing) that could be tightened.

2 / 3

Actionability

Provides copy-paste-ready docker compose, docker exec, and lsof commands with concrete hostnames, ports, container names, and DB credentials, and explicitly explains the php-X.Y / phpXX placeholder substitution.

3 / 3

Workflow Clarity

Pre-flight validation checkpoints ('derive PHP version before standing anything up', lsof port checks before start) and a symptom-to-layer-to-first-check troubleshooting table provide explicit feedback loops for error recovery.

3 / 3

Progressive Disclosure

The file is well-sectioned with clear headers, but it is a single ~200-line monolith with no bundle files; the available-services matrix and troubleshooting table are inline reference material that could plausibly be split into separate files.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with explicit trigger guidance and good coverage of natural user terms including paste-able error strings. It cleanly separates its niche from sibling skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'how to shell into PHP containers', 'how to access the DB', 'LOCAL_SRC mounting convention', and troubleshooting 'containers that won't start or keep crashing, image build failures' — rather than vague language.

3 / 3

Completeness

An explicit 'Use whenever the user asks about...' clause answers both what the skill does and when to use it, in third person.

3 / 3

Trigger Term Quality

Covers natural phrasing a developer would say ('running OrangeHRM locally', 'switching PHP versions', 'accessing the dev database') plus literal error strings they would paste ('port is already allocated', 'database connection refused').

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to the OrangeHRM Docker dev environment with distinct triggers and explicit pointers to sibling skills, so it is unlikely to fire for the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
orangehrm/orangehrm
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.