agentleFS
Sign inStart free
GoogleKnown publishergoogle/boringssl/_agents/skills/run_ssl_go_tests/SKILL.md

run-ssl-go-tests

Skill2.3k starsChanged 26 days agoApache-2.0View on GitHub

How to run BoringSSL's ssl/test/runner suite (protocol-level BoGo tests)

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about google/boringssl

The biggest 5 of 44 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 44

Talked about on GitHub, Stack Overflow, Hacker News and Bluesky (44 times).

On GitHub · 37

32 more on GitHub

On Hacker News · 1

On Bluesky · 1

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Overview and Running: Read ssl/test/README.md for an overview of the test suite and basic instructions on how to run it manually using go …

    line 12

≈ “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

Running BoringSSL Protocol-Level Tests (BoGo Tests aka blackbox tests)

This skill describes how to run and configure BoringSSL's protocol-level test suite, which uses a Go-based test harness (runner) and a C++ shim (bssl_shim).

To run and work with these tests, you must refer to the following documentation:

  1. Overview and Running: Read ssl/test/README.md for an overview of the test suite and basic instructions on how to run it manually using go test in the ssl/test/runner directory.
  2. Build Integration: Refer to BUILDING.md (specifically the "Running Tests" section) for how these tests are integrated into the CMake/Ninja build system (e.g., ninja run_tests).

Quick Reference

  • Running all tests via Go:
    cd ssl/test/runner && go test
  • Listing/Filtering flags: To see available flags for the runner, build the test binary and run with -help:
    cd ssl/test/runner
go test -c
./runner.test -help

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