Add consent-aware X/Twitter collection with TweetClaw

[kriptoburak]

Summary

• Add an optional x-twitter-deep-profile-collect sub-skill for Magic Mirror.
• Discover current read capabilities through TweetClaw's explore catalog instead of hard-coding paths.
• Require explicit consent for likes, following, followers, and raw-list retention.
• Install from the recommended ClawHub source, with npm documented as a fallback.

Independent Repository Fixes

• Replace the broken Discussions link with the repository's working Issues route.
• Correct the parent skill's inaccurate claim that every platform has a fixed workflow file.
• Minimize stored social data by default and document deletion behavior.
• Align privacy claims across the README and parent skill.

Validation

• Parsed both Skill frontmatter blocks as YAML.
• Verified balanced Markdown fences and clean diffs.
• Verified every reachable Markdown link. The existing Discord invite timed out from the validation runner.
• Verified the install command and disclosure against the current TweetClaw README.
• Confirmed no fixed Xquik API paths remain in the sub-skill.

Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.

[kriptoburak]

Repair pushed in 862c5e3 after a full PR audit.

The update removes fixed endpoint assumptions, requires explicit consent for account-scoped signals, makes raw-list retention opt-in, and uses TweetClaw's live capability catalog. It also fixes the repository's broken Discussions link, inaccurate workflow-file claim, and broad raw-data retention guidance.

All current comments, reviews, review threads, checks, commits, events, and the full diff were reviewed. There are no unresolved review requests.

Xquik is an independent third-party service. Not affiliated with X Corp. "Twitter" and "X" are trademarks of X Corp.

[kriptoburak]

Consolidated the focused branch into signed commit 714ae95. I removed unrelated punctuation churn while preserving TweetClaw collection, explicit consent, minimal retention, deletion, live capability discovery, broken-link, and workflow-documentation repairs. Both skills validate, all public dependencies return HTTP 200, and GitHub verifies the signature.