Hacker News

New stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Show HN: Pi-jev-auto-mode – a probability model gates Pi's shell commands(github.com/jomatsu ↗)
    discuss
  2. Inside OpenAI’s agentic software factory(pragmaticengineer.com ↗)
    discuss
  3. Don't Just Say Hello(nohello.net ↗)
    discuss
  4. Saturn's South Pole Features Newly Formed Atmospheric Decagon(universetoday.com ↗)
    discuss
  5. 256GB Mac Mini is too small. You need Elbowroom(tomjohnell.com ↗)
    discuss
  6. AI could create a 'silicon species' that rivals humans, Microsoft chief warns(euronews.com ↗)
    discuss
  7. Migrating the GitHub Copilot Runtime to Rust, Using Copilot(github.blog ↗)
    discuss
  8. Show HN: Telly, talk to your Mac and it does the clicking(hey-telly.com ↗)
    1comments
  9. More Kiwis taking 'hands off' approach with self-driving technology(rnz.co.nz ↗)
    discuss
  10. Robots are asking for tips. But who gets the money?(bbc.com ↗)
    discuss
  11. Typesafe's Jev is the fish at the poker table(backnotprop.com ↗)
    discuss
  12. DuckDB Queries Inside MySQL(villagesql.com ↗)
    1comments
  13. Monobloc Chair(wikipedia.org ↗)
    discuss
  14. Novgraph: Knowledge graph for codebases that saves you 99% percent tokens
    discuss
  15. What happens when you send a message to an LLM (the API call explained)(heymeraki.substack.com ↗)
    1comments
  16. When Software Outlives Its Reasons (Philosophical Essay)(ssrn.com ↗)
    discuss
  17. KIDS Act(europa.eu ↗)
    discuss
  18. Play Hamster Inn Game Now: Build Your Dream Hotel(hamster-inn-game.pages.dev ↗)
    discuss
  19. A Feather Found in Dinosaur Poop Might Explain How Birds Beat Extinction(nytimes.com ↗)
    discuss
  20. VortexKV – 6.8M ops/s pure Go Redis alternative with Web Studio
    discuss
  21. Review-comments.nvim: Do code review in Neovim – pass review comments to agents(github.com/narqo ↗)
    discuss
  22. Goldman Sachs – Physical AI(finvaulta.com ↗)
    1comments
  23. How macOS Works(macinternals.app ↗)
    discuss
  24. Poll: Bi-partisan supermajority see serious risk of AI destroying humanity(politico.com ↗)
    1comments
  25. The Auroral Oval [pdf](jhuapl.edu ↗)
    discuss
  26. Streaming real-time HDR reflections to every device(miris.com ↗)
    discuss
  27. Adventures in Microcontroller Circuit Debugging(bigmessowires.com ↗)
    discuss
  28. A supermajority wants to slow AI down(natesilver.net ↗)
    1comments
  29. Show HN: The Endless Museum, Wikipedia as a walkable museum(theendlessmuseum.com ↗)
    discuss
  30. How India Built (and Broke) the Biggest Options Casino(bloomberg.com ↗)
    1comments

Show HN: Linting 216 public Claude Code skills – 69% won't reliably trigger

1 pointsby 1h agoskillcrossroads.com
0 comments
I built a linter for Claude Code artifacts (skills, subagents, slash commands, .mcp.json configs, and plugins) and then pointed it at a pile of public repos to see what people actually ship. A few of the numbers surprised me enough that I wrote them up.

The one that stuck: across 87 public subagents, 57% (50 of 87) declare no `tools` list at all. That reads like a safe default, but it's the opposite. A subagent with no `tools` inherits the caller's entire toolbox, Bash included. Permission prompts still gate execution, but a worker you meant to "just read code" now carries the grant surface to run shell — the opposite of least-privilege. Add 16 more that grant bare `Bash` and 8 that grant a wildcard, and 85% of the sample isn't least-privilege.

Other findings from the two scans:

- Of 215 public skills scored for triggering, 69% have a `description` that won't reliably trigger (40% outright unlikely to fire, 28% borderline). "My skill never fires" is the #1 real-world failure, and it hides in one frontmatter line. - 83% of subagents (72 of 87) lack invocation cues ("use when…") in their description. - 1 of 216 skills, and 0 of 87 subagents, pass every check cleanly. Almost everyone got secrets right: only 6 of 216 skills tripped the scanner.

How it works: mostly pure, deterministic checks that emit file:line evidence ("SKILL.md:14 links ./references/converter.md, not found"). An optional LLM check (bring your own key) judges whether a description will actually trigger. The CLI is free (`npx skillcrossroads ./my-skill`), there's a GitHub Action that gates PRs, and it's open-core: the public audits are free, money is a hosted Pro tier.

Limits: the two reports ran different editions (skills on rubric v1.2 with the LLM checks, agents on v1.2 deterministic-only), both labeled, tree SHAs pinned, reproduction commands published. The rubric is strict on purpose, and every finding carries file:line evidence you can check against the artifact itself. The sample is 216 skills across 18 repos and 123 agents/commands (87 subagents + 36 commands) across 10 repos, caps disclosed, and you can re-run it on your own repos.

Reports: https://skillcrossroads.com/report?ref=hn-show and https://skillcrossroads.com/report-agents?ref=hn-show Code: https://github.com/sgharlow/skillcrossroads

A quiet thread, for now.Start the conversation on HN ↗