Skip to content

Add scoped X public data source#8

Open
kriptoburak wants to merge 1 commit into
elementalsouls:mainfrom
kriptoburak:codex/add-xquik-public-x-recon
Open

Add scoped X public data source#8
kriptoburak wants to merge 1 commit into
elementalsouls:mainfrom
kriptoburak:codex/add-xquik-public-x-recon

Conversation

@kriptoburak

Copy link
Copy Markdown

Description

Adds a scoped X/Twitter public-data source to the offensive OSINT tooling quick-install section, with an install command pinned to the current x-developer package. The copy keeps the use case limited to authorized public-source collection and avoids private account access or publishing workflows by default.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New section / capability (non-breaking change which adds functionality)
  • Wordlist / catalog expansion (non-breaking)
  • Vendor fingerprint / secret pattern / dork addition (non-breaking)
  • Documentation update
  • Renumbering / restructuring (potentially breaking)
  • Test addition (smoke-test prompt)

Affected skills

  • osint-methodology
  • offensive-osint
  • Both
  • Repo infrastructure only (READMEs, docs, CI, etc.)

Affected sections (if applicable)

  • arsenal §46.13

Checklist

  • My change is OSINT-only (no active exploitation, post-exploit, malware tradecraft).
  • I updated CHANGELOG.md under [Unreleased].
  • I updated the README's "What's in the box" tables (if I added a section).
  • I added trigger phrases to the YAML frontmatter (if I added a new triggerable concept).
  • I added a self-test prompt to tests/smoke-test-prompts.md (if I added a new capability).
  • Severity / detectability / confidence tags are consistent with existing rubrics.
  • I tested locally (installed the modified skill in Claude Code and verified the relevant prompts).
  • My commits follow the format <type>(<scope>): <subject>.

Sample prompt that exercises this change

Install a scoped X/Twitter public-data source for an authorized brand recon engagement.

Expected response

Claude should route to arsenal §46.13, give the pinned x-developer@2.4.16 install command, link to Xquik docs, and keep the workflow limited to authorized public X/Twitter collection.

Related issues

None.

Additional notes

Validation run:

  • git diff --check
  • YAML frontmatter parse for both SKILL.md files
  • python3 -m py_compile skills/offensive-osint/scripts/secret_scan.py skills/offensive-osint/scripts/h1_reference.py
  • npm view x-developer@2.4.16 version
  • curl -L https://docs.xquik.com

Default markdownlint was not clean on the existing repository before isolating this patch. I did not rewrite unrelated historical markdown style issues.

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.

1 participant