docs: add approved X source packet guidance#24
Conversation
|
@kriptoburak is attempting to deploy a commit to the cgallic's projects Team on Vercel. A member of the Team first needs to authorize it. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e740bb11fb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| - search tweets for brand, competitor, problem, and category language | ||
| - search tweet replies for objections, praise, and comparison language | ||
| - scrape approved tweet URLs supplied by the operator |
There was a problem hiding this comment.
When this skill is used for an X source packet, this newly allowed task permits scraping tweet URLs after only operator approval, but the repo's social automation guardrail explicitly applies to data collection/listening jobs and blocks scraping or enrichment outside approved APIs and retention terms (harness/references/social-automation-rules.md). Operator approval of TweetClaw as a source is not the same as an approved X developer/API path, so this can steer brand-pulse runs into noncompliant X evidence collection; require the official/approved API path and retention constraints here before allowing tweet scraping.
Useful? React with 👍 / 👎.
|
Addressed the Codex note in b02b7d9 by requiring the social automation rules to clear the X collection path and by making approved API/developer-policy authorization and retention constraints explicit before any TweetClaw collection task. |
|
Optional visibility note: if this is useful and you merge it after checks pass, feel free to share the PR on X/Twitter and tag https://x.com/burakbayir. I can repost it to my 24k followers so more developers and power users can discover this repo. |
1 participant
Summary
kai-brand-pulse.Validation
git diff --checknpx --yes markdown-link-check harness/skills/kai-brand-pulse/SKILL.md --quietpython3 scripts/quality_gates/banned_word_check.py --file harness/skills/kai-brand-pulse/SKILL.mdpython3 -m pytest tests/test_brand_pulse.pyNo write or account-mutating action is enabled by this doc change; those remain explicitly approval-gated.