Code-eval runners are Lambda handler test fixtures (Node + Python). They

scripts/code-eval-runners/

promptBeginner5 min to valuemarkdown0

0 views

May 30, 2026

Loading actions...

Code-eval runners are Lambda handler test fixtures (Node + Python). They

intentionally execute user-supplied evaluator source via `exec` / dynamic

`import` and talk to a locally-provisioned Floci endpoint from

`urllib.request.urlopen`. Both are by design and inherent to the runner

contract — scanning them produces noise, not signal.

scripts/code-eval-runners/

View Original Source

Related Skills

General

PromptBeginner5 minmarkdown

<h1 align="center">

163

Jan 12, 2026

General

PromptBeginner5 minmarkdown

Frontend Typescript Linting.mdc

TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend linting, type safety, or ESLint configuration.

119

Feb 15, 2026

General

PromptBeginner5 minmarkdown

2. Apply Deepthink Protocol (reason about dependencies

risks

109

Jan 15, 2026

Code-eval runners are Lambda handler test fixtures (Node + Python). They

Code-eval runners are Lambda handler test fixtures (Node + Python). They

intentionally execute user-supplied evaluator source via exec / dynamic

import and talk to a locally-provisioned Floci endpoint from

urllib.request.urlopen. Both are by design and inherent to the runner

contract — scanning them produces noise, not signal.

Related Skills

<h1 align="center">

Frontend Typescript Linting.mdc

2. Apply Deepthink Protocol (reason about dependencies

Code-eval runners are Lambda handler test fixtures (Node + Python). They

intentionally execute user-supplied evaluator source via exec / dynamic

import and talk to a locally-provisioned Floci endpoint from

urllib.request.urlopen. Both are by design and inherent to the runner

contract — scanning them produces noise, not signal.

intentionally execute user-supplied evaluator source via `exec` / dynamic

`import` and talk to a locally-provisioned Floci endpoint from

`urllib.request.urlopen`. Both are by design and inherent to the runner

intentionally execute user-supplied evaluator source via `exec` / dynamic

`import` and talk to a locally-provisioned Floci endpoint from

`urllib.request.urlopen`. Both are by design and inherent to the runner