About

Imported from yusukebe/skills (skills/rj/SKILL.md). Install upstream with npx skills add yusukebe/skills --skill rj. Copyright stays with the author.

rj

Name: rj
Author: yusukebe

rj is a small CLI for printing the metadata of an HTTP response as JSON: status code, headers, protocol, and timing breakdown. It does not print the response body — for that, keep using curl. The two are complementary: curl for the body, rj for everything around it.

Install

brew install yusukebe/tap/rj

Binaries and go install are also available — see the repo.

Usage

rj https://skills.yusuke.run/skills.json

Output looks like:

{
  "code": 200,
  "header": { "content-type": "application/json" },
  "protocol": "HTTP/1.1",
  "status": "200 OK",
  "timing": { "dns_lookup": 0.48, "tcp_connection": 0.21, ... }
}

Pipe into jq to extract specific fields:

rj https://skills.yusuke.run/ | jq '.header'
rj https://skills.yusuke.run/ | jq '.code'

Common flags:

-X POST — change method.
-H 'Header: value' — add a request header.
-u user:pass — Basic auth.
--http3 / --http1.1 — pin HTTP version.

When to use

Confirming response headers (content-type, cache-control, custom X-* headers).
Verifying that an endpoint returns the expected status code.
Checking how a request is routed (HTTP version, timing breakdown).
Scripted health checks that need a structured view of the exchange.

For inspecting the response body, reach for curl (and pipe through jq if it's JSON). Use rj when the wrapper around the body is what matters.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

yaml

targets:
  - https://api.opensmartroute.ai/api/v1/registry/yusukebe-skills-rj/manifest   # or paste the manifest below

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

yusukebe-skills-rj.ocm.jsonjson

{
  "ocm": "1",
  "id": "yusukebe-skills-rj",
  "kind": "skill",
  "name": "rj",
  "description": "yusukebe/rj is a tiny CLI that fetches a URL and prints the response metadata (status, headers, protocol, timing) as JSON. It does not print the body — use it alongside `curl`, not as a replacement.",
  "publisher": "yusukebe",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "cli",
      "http",
      "json",
      "debugging",
      "github"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "yusukebe/rj is a tiny CLI that fetches a URL and prints the response metadata (status, headers, protocol, timing) as JSON. It does not print the body — use it alongside `curl`, not as a replacement."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github",
      "repository": "https://github.com/yusukebe/skills",
      "path": "skills/rj/SKILL.md",
      "ref": "7b3a6c2b2930d90304f1b44954fdc1a1a70d26be",
      "url": "https://github.com/yusukebe/skills/blob/7b3a6c2b2930d90304f1b44954fdc1a1a70d26be/skills/rj/SKILL.md",
      "key": "yusukebe/skills/skills/rj/SKILL.md"
    }
  },
  "instructions": "# rj\n\n`rj` is a small CLI for printing the **metadata** of an HTTP response as JSON: status code, headers, protocol, and timing breakdown. It does **not** print the response body — for that, keep using `curl`. The two are complementary: `curl` for the body, `rj` for everything around it.\n\n## Install\n\n```sh\nbrew install yusukebe/tap/rj\n```\n\nBinaries and `go install` are also available — see the repo.\n\n## Usage\n\n```sh\nrj https://skills.yusuke.run/skills.json\n```\n\nOutput looks like:\n\n```json\n{\n  \"code\": 200,\n  \"header\": { \"content-type\": \"application/json\" },\n  \"protocol\": \"HTTP/1.1\",\n  \"status\":",
  "cost": {
    "context_tokens": 361
  }
}

Fetch it by URL: GET /api/v1/registry/yusukebe-skills-rj/manifest?version=1.0.0

Reviews

Star ratings from people who tried it. One review per account; edit yours any time.

No reviews yet. Install it, try it, and be the first to rate it.