CtrlK
BlogDocsLog inGet started
Tessl Logo

build-paths-advanced

Scaffold an agent system where Oracle AI DB is the *only* state store, composed from the build-paths/skills/ building-block library. Stack — langchain-oracledb + oracle-database-mcp-server + in-DB ONNX embeddings + OCI GenAI Grok 4 + Open WebUI. Three projects — production-feeling NL2SQL+RAG hybrid analyst, self-improving research agent, conversational schema designer. For users who want a real DB-as-only-store agent demo.

63

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./build-paths/advanced/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is a highly actionable, well-sequenced orchestration skill with explicit validation and recovery loops, delegating reference material to clearly signaled one-level-deep files. Its only real weakness is length and some redundancy around the core constraint.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence with no basic-concept filler, but at ~230 lines it restates the 'only state store'/forbidden-imports rule across Step 0, Step 3c, Step 4, and 'What you must NOT do', so it could be tightened.

2 / 3

Actionability

Provides copy-paste-ready commands (onnx2oracle load, grep -RE forbidden-imports, docker compose up -d, jupyter nbconvert --execute), exact file paths, env vars, and model names, with only a few explicitly acknowledged skeleton loops as placeholders.

3 / 3

Workflow Clarity

Clear Step 0-5 sequence with explicit validation (verify.py checks, OAMP cold-to-warm round-trip, per-idea smoke) and a stated feedback loop ('follow shared/verify.md recovery loop, max 3 retries') for the database operations involved.

3 / 3

Progressive Disclosure

Delegates heavy material to clearly signaled one-level-deep references (Step 0 list and inline 'See shared/references/oamp.md for the full decision tree') instead of reproducing it, keeping the body an orchestration overview with easy navigation.

3 / 3

Total

11

/

12

Passed

Description

67%

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

The description is sharply specific and highly distinctive, but it leans on technical jargon and lacks an explicit 'Use when...' trigger clause, leaving the 'when to use' guidance only implied. Adding a natural-language trigger phrase would lift the trigger-term and completeness dimensions.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when a user wants to build an Oracle AI DB agent demo with the database as the only state store.'

Soften jargon with at least one user-natural phrasing (e.g. 'Oracle-backed agent', 'database-as-only-store') alongside the stack component names so users would naturally say the trigger terms.

Keep the three named project types but pair them with a 'Use when the user asks for...' framing to make the when-to-use intent explicit rather than implied.

DimensionReasoningScore

Specificity

Lists concrete actions ('Scaffold an agent system') plus a named stack and three specific project types (NL2SQL+RAG hybrid analyst, self-improving research agent, conversational schema designer), matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

The 'what' is explicit, but 'when' is only weakly implied via 'For users who want a real DB-as-only-store agent demo' with no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Relevant domain keywords are present (Oracle AI DB, NL2SQL, RAG, agent) but the phrasing is jargon-heavy ('langchain-oracledb', 'OCI GenAI Grok 4', 'in-DB ONNX') with no natural user-facing trigger variations, matching 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

The 'Oracle AI DB is the only state store' constraint plus three narrowly named project types form a distinct niche with triggers unlikely to conflict with other skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

10

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

14

/

16

Passed

Repository
oracle-devrel/oracle-ai-developer-hub
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.