agentleFS
Sign inStart free
httprunnerhttprunner/skills/result-bitable-reporter/SKILL.md

result-bitable-reporter

Skill2 starsChanged 9 months agoMITView on GitHub

Filter rows from sqlite capture_results and report to Feishu Bitable with retry-safe sqlite writeback. Use for stat/filter/report/retry-reset workflows, especially task-scoped reporting with --task-id.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill to run a deterministic sqlite -> Feishu Bitable pipeline around capture_results.

    line 8
  2. Very specific:

    Default status filter is reported IN (0,-1).

    line 15
  3. Very specific:

    Use npx tsx scripts/result_reporter.ts --help as the CLI source of truth.

    line 33
  4. Very specific:

    Use report --dry-run to validate selection before network writes.

    line 73
  5. Very specific:

    Check sqlite report_error for root cause when reported=-1.

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Result Bitable Reporter

Use this skill to run a deterministic sqlite -> Feishu Bitable pipeline around capture_results.

Workflow

  1. Select rows
  • stat: print total sqlite row count for one --task-id.
  • filter: preview upload candidates from capture_results.
  • Default status filter is reported IN (0,-1).
  1. Report rows
  • report: batch create to Feishu Bitable and write back sqlite status.
  • --max-rows <n> sets total cap for one report run.
  • For per-task workflows, always pass --task-id <TASK_ID> to avoid cross-task uploads.
  • Success writeback: reported=1, reported_at=now_ms, report_error=NULL.
  • Failure writeback: reported=-1, reported_at=now_ms, report_error=<truncated error>.
  1. Retry failures
  • retry-reset: move failed rows (reported=-1) back to pending (reported=0), then rerun report.

Run

npx tsx scripts/result_reporter.ts <subcommand> [flags]

Use npx tsx scripts/result_reporter.ts --help as the CLI source of truth.

Environment Variables

Required for report:

  • FEISHU_APP_ID
  • FEISHU_APP_SECRET
  • RESULT_BITABLE_URL

Optional overrides:

  • FEISHU_BASE_URL (default https://open.feishu.cn)
  • TRACKING_STORAGE_DB_PATH (default $HOME/.eval/records.sqlite)
  • RESULT_SQLITE_TABLE (default capture_results)

Recommended Command Patterns

Task-scoped preview:

npx tsx scripts/result_reporter.ts filter --task-id <TASK_ID> --status 0,-1 --limit 20

Task-scoped report:

export FEISHU_APP_ID=<app_id>
export FEISHU_APP_SECRET=<app_secret>
export RESULT_BITABLE_URL='https://.../wiki/...?...table=tbl_xxx&view=vew_xxx'
npx tsx scripts/result_reporter.ts report --task-id <TASK_ID> --batch-size 100 --max-rows 500

Retry failed rows:

npx tsx scripts/result_reporter.ts retry-reset --app com.tencent.mm --scene onSearch
npx tsx scripts/result_reporter.ts report --task-id <TASK_ID> --status 0,-1

Failure Handling

  • Use report --dry-run to validate selection before network writes.
  • Check sqlite report_error for root cause when reported=-1.
  • Fix root cause, then rerun retry-reset and report.

Resources

  • scripts/result_reporter.ts: CLI behavior and flags.
  • references/sqlite-and-field-mapping.md: sqlite schema and field mapping.
  • references/feishu-api-and-errors.md: Feishu API contract and error triage.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free