oprogramadorreal/optimus-claude / skills/how-to-run
how-to-run
FlaggedGenerates or updates a project's HOW-TO-RUN.md — one verified document teaching a new developer to set up their environment and run the project locally. Detects toolchain, source dependencies, external services, and env config via a read-only agent; audits an existing file against actual project state and offers a display-only guided walkthrough. Never runs setup commands; writes only HOW-TO-RUN.md.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 4.5 KB |
| SKILL.md | skill md | 15.0 KB |
| agents/how-to-run-auditor.md | markdown | 6.2 KB |
| agents/openai.yaml | config | 198 B |
| agents/project-environment-detector.md | markdown | 34.9 KB |
| agents/shared-constraints.md | markdown | 1.7 KB |
| references/detector-framework-config-services.md | markdown | 4.3 KB |
| references/detector-native-and-embedded.md | markdown | 1.7 KB |
| references/external-services-docker.md | markdown | 29.4 KB |
| references/guided-walkthrough.md | markdown | 5.5 KB |
| references/how-to-run-sections.md | markdown | 20.9 KB |
| references/step6-verification-audits.md | markdown | 11.5 KB |
references/detector-framework-config-services.md
View on GitHub# Task 5b — External services from framework config files
- **Matching:** tolerantly parse top-level keys (well-formedness not required). Flag a section whose **name** whole-token-matches (case-insensitive, full top-level key, not substrings): `redis`, `mongo`, `mongodb`, `nosql`, `database`, `db`, `connectionstring`, `connectionstrings`, `connection_string`, `datasource`, `authority`, `oidc`, `openidconnect`, `identity`, `auth0`, `cognito`, `okta`, `keycloak`, `firebase`, `firestore`, `aws`, `s3`, `sns`, `sqs`, `storage`, `blob`, `queue`, `bus`, `messaging`, `elastic`, `search`, `rabbitmq`, `kafka`, `smtp`, `mail`, `license`, `licensemanager` — or any section whose values contain an external-FQDN-shaped string. A `<Vendor>Settings` / `<Vendor>Config` / `<Vendor>Options` section containing an FQDN in its values is always flagged. Treat each child of a top-level `spring` key (YAML, or the `spring.` prefix of `.properties` keys) as its own section named by its dotted path, one level deeper under `spring.data` (`spring.datasource`, `spring.data.redis`); this overrides the `.properties` collapse below.
- **Hostname check:** lowercase the candidate first, then require `^[a-z0-9]([a-z0-9.-]*[a-z0-9])?\.[a-z]{2,}(:\d{1,5})?/?$` — anchored end-of-string (rejects appended junk like `` api.host.com`ls` ``), and rejects `localhost` and IP literals. Before matching, drop placeholders: exactly `example.com` / `example.org` / `example.net` / `example` / `test` / `invalid`; any subdomain of the RFC 2606/6761 reserved TLDs `test` / `example` / `invalid` / `localhost`; hostnames equal to or ending in `.local`, `.home.arpa`, `.internal`, `.localdomain`, `.lan`, `.corp` (private endpoints); and the labels `your-domain`, `yourdomain`, `changeme`, `placeholder`.
- **Extract per match:** service name (the section name as it appears, then title-cased — or the database product, below), source `<file>:<line>`, one representative endpoint (first FQDN in the section's values, else the string `shared-cloud endpoint`), best-guess type (`database` / `cache` / `queue` / `storage` / `identity` / `api` / `email` / `search` / `license` / `other`), and `Endpoint semantics`: for `database`-type matches only, scan connection-string-shaped values (its key or a parent key matches `(?i)connection.?string|datasource|connectionuri|connection_uri|database.?url|dburl|mongodb_url|mongodb_uri|mongo_uri|server` and the value's first character isn't `{` / `[`) and apply the classifiers in this precedence order (not the return format's listing order): `local-windows-auth` → `local-socket` → `local-named-instance` → `local-default` → `remote`; drop to `ambiguous` when the file is unreadable or nothing matches; non-database matches emit `remote` when the representative endpoint is an FQDN, else `—`. Name a `database`-type match for its product when those same values identify it unambiguously — a URI scheme (`postgresql://`, `postgres://`, `mysql://`, `mongodb://`, `mongodb+srv://`, `jdbc:sqlserver:`, …) or vendor-only keywords (`Initial Catalog=`, `Trusted_Connection=`, `(localdb)` → SQL Server; `Host=` with `Username=` → PostgreSQL) — spelled `SQL Server`, `PostgreSQL`, `MySQL`, `MariaDB` or `MongoDB`. `Server=` with `Database=` alone is ambiguous (MySQL and Npgsql use it too): keep the section name.
- **Sanitization:** never use a value as the representative endpoint when its key matches `(?i)(key|secret|password|token|credential|private)`. Reject an endpoint on a case-insensitive match of `^(file|javascript|data|mailto|vbscript|blob):`, on any Cc/Cf control character, or on an empty/`..` path segment after splitting the path portion on `/`. Sanitize the section name with `^:?[A-Za-z_][A-Za-z0-9_.-]{0,63}$` (optional leading `:` for Elixir atoms, `.` for dotted keys; rejects backticks, angle brackets, whitespace, parentheses, markdown metacharacters) before title-casing — drop the match on failure. For `.properties` files, collapse each key to its pre-first-`.` prefix (`spring.datasource.url` → `spring`) and apply the allowlist to the collapsed form. Apply Task 0b path validation to the `<file>` field.
- **Caps:** 20 services per config file (then one `N+ more — see <file>` line); 60 total across all files (report the first 60 and state the overflow).
- **Confidence:** every Task 5b match is `candidate`; the main skill renders the marker and owns every user prompt.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |