Skip to content

Add falsegreen-skill to Community Plugins - #50

Merged
kantorcodes merged 1 commit into
hashgraph-online:mainfrom
vinicq:add-falsegreen-skill
Jul 3, 2026
Merged

Add falsegreen-skill to Community Plugins#50
kantorcodes merged 1 commit into
hashgraph-online:mainfrom
vinicq:add-falsegreen-skill

Conversation

@vinicq

@vinicq vinicq commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Adds one entry to Community Plugins -> Development & Workflow for falsegreen-skill.

It is a test-quality skill for coding agents (Claude Code, Codex, Gemini) that detects false-positive tests: tests that keep passing green even when the code under test is broken. It applies a J1-J6 judgment framework (does the assertion run, does the value come from an independent oracle, is the real unit tested, etc.) across Python, TypeScript, JavaScript, and Robot Framework.

Single additive line, inserted alphabetically. One-sentence description per CONTRIBUTING.md.

Scanner CI

The HOL Plugin Scanner now runs in CI on the source repo via a dedicated workflow (.github/workflows/plugin-scanner.yml), on every push and pull request, failing on any high/critical finding.

Scanner actions are SHA-pinned to keep the Operational score clean.

Test-quality skill that detects false-positive tests: https://github.com/vinicq/falsegreen-skill
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@vinicq

vinicq commented Jun 29, 2026

Copy link
Copy Markdown
Contributor Author

Updated the plugin: the HOL plugin-scanner now reports 90/142 (grade A), 0 high/critical on vinicq/falsegreen-skill (was 72/142). The earlier HARDCODED_SECRET findings were JWT literals in a TypeScript example fixture (not real credentials); they're renamed to obvious placeholders, plus a lockfile and SHA-pinned Actions. Ready for re-scan whenever convenient.

@vinicq

vinicq commented Jul 2, 2026

Copy link
Copy Markdown
Contributor Author

Done. Added .github/workflows/plugin-scanner.yml to vinicq/falsegreen-skill, running the HOL Plugin Scanner on every push and pull request (fails on high/critical).

The scanner actions are SHA-pinned so the workflow doesn't cost points on its own Operational check. I also linked the run and score in the PR description. Ready for re-review whenever convenient.

@kantorcodes
kantorcodes merged commit 48d054d into hashgraph-online:main Jul 3, 2026
@kantorcodes

Copy link
Copy Markdown
Member

🎉 Hey @vinicq, your plugin has been merged and is now listed in the HOL Registry!

Claim your plugin

As the author, you can verify ownership of your plugin to unlock:

  • Owner-verified badge on your plugin's registry listing
  • Trust score visibility and analytics for your plugin
  • Direct claim link to share with your community
  • Dashboard access at hol.org/guard/plugins to track installs, trust, and engagement

How to claim

  1. Visit hol.org/guard/plugins
  2. Find your plugin and click "Verify ownership"
  3. Sign in with GitHub — we only request read:user, user:email, and read:org (no write access to your repos)
  4. We verify you own the repository, and your plugin gets the ✅ owner-verified badge

The whole process takes under 30 seconds. No need to add any secrets or tokens to your repo — verification is done entirely through GitHub OAuth.

If you have any questions, feel free to ask here or reach out at support@hol.org.

vinicq added a commit to vinicq/falsegreen-skill that referenced this pull request Jul 29, 2026
The entry merged in hashgraph-online/awesome-ai-plugins#50 was removed 11 days
later by that repo's sync bot, which overwrites its own README with the one from
hashgraph-online/awesome-codex-plugins. The mirror is not a writable surface, so
the submission goes upstream, where the validator is stricter.

Two hard failures in scripts/validate-plugin-pr.py, both fixed here:
interface.composerIcon was absent from the Codex manifest, and the repo had no
icon asset at all. The icon is a broken green check, 413 bytes, pure vector, no
raster payload, legible at 32px.

Also fixes a real host defect: skills/falsegreen-skill/SKILL.md mandated loading
reference.md in full for any non-Python file, while contexts/codex.md documents
in this same repo that its ~90 KB never fits the ~32 KiB Codex budget and
truncates mid-file without warning. That silently under-detects TypeScript,
JavaScript and Robot Framework. The load is now section-scoped, with the compact
fragments/* tables named as the entry point for budget-constrained hosts.

The scanner workflow now matches the filename and the settings that the upstream
PR checklist names. min_score was unset, so the action ran with MIN_SCORE: 0 and
the score gate was never enforced. The header comment cited the wrong repo and a
score scale that no longer exists.

Closes #166
@vinicq

vinicq commented Jul 29, 2026

Copy link
Copy Markdown
Contributor Author

@kantorcodes heads up, since you merged this one: the entry is no longer in the README here.

It was removed on 2026-07-14 by c653369f ("chore: sync from upstream registries"), because .github/workflows/sync-from-upstream.yml replaces this repo's README with the one from hashgraph-online/awesome-codex-plugins:

- name: Sync README from codex
  run: cp codex-source/README.md README.md

Upstream never had the line, so plugins.json was regenerated without it and the plugin never reached the registry. That is also why the claim flow at hol.org/guard/plugins finds nothing for it yet.

I resubmitted at the source rather than reopening anything here:

That PR also covers what this repo's guide did not require at the time: interface.composerIcon and an assets/icon.svg in the plugin repo, plus the scanner workflow renamed and aligned with the upstream template. I ran validate_remote_repo("vinicq", "falsegreen-skill") from your validator against the published repo first: 0 errors, 0 warnings.

Nothing needed on this PR. Leaving the note here so the trail is not confusing for anyone who finds the merge and then cannot find the entry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants