AC oracle-x-bist
Read and reason about Borsa İstanbul — BIST equities and the XU100, TEFAS funds and their holdings, KAP disclosures, VİOP futures margins, open interest and positioning, foreign ownership, short-sale restrictions, and the Turkish macro series (TÜFE inflation, policy rate, USDTRY) the rest is measured against. Use this whenever a question names a Turkish ticker such as THYAO, ASELS, GARAN or EREGL, a BIST index, a TEFAS fund code, KAP, VİOP or Takasbank, or asks what a lira return was actually worth. Half of it needs no server at all: how a nominal return is turned into a real one, where Takasbank publishes the price scan range and the two filters that make it read correctly, and why a margin-call price for VİOP cannot be computed from anything public. The other half calls a running Oracle-X instance when ORACLE_X_URL is set. Consult it before quoting any Turkish figure, because a lira number over a year of ~32% inflation reports inflation as performance.
Read and reason about Borsa İstanbul — BIST equities and the XU100, TEFAS funds and their holdings, KAP disclosures, VİOP futures margins, open interest and…
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Read and reason about Borsa İstanbul — BIST equities and the XU100… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 75Steps. 3 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2241 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 968: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +4Structure: 12 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.