domains / families / research / jev-social

jev-social

combined

Run browser-grounded social research without remote account mutations through Jev Social when a user wants posts, profiles, comments, video evidence, or a source-linked report from Instagram, TikTok, or LinkedIn and the local socai CLI reports support for that platform. Do not use for publishing, engagement actions, or general web research. Run read-only, browser-grounded Instagram, TikTok, or LinkedIn research through Jev routing and socai CLI, returning source-linked evidence and reports.

When to use

• Use when a user requests evidence-backed research on Instagram, TikTok, or LinkedIn and wants real public posts or profiles rather than a general web summary.
• Use when the user wants a fast demonstration with streamed progress, previewable post or video cards, and a final research report.
• Use when the local socai CLI and the requested platform both pass the Jev Social readiness check.
• Do not use for publishing, commenting, liking, following, messaging, account growth automation, or unrelated web research.

When not to use

• Platform support depends on the installed socai build, the user's authenticated local session, and what the page actually exposes at run time.
• Platform-read-only operation does not mean a write-free filesystem: the CLI stores run records and can download requested TikTok media locally.
• Search results can be incomplete, personalized, rate-limited, stale, or empty; the skill cannot guarantee coverage or ranking completeness.
• A search card is not a fully read post. Claims about details require a successful detail read recorded in the action history.
• Captured posts and comments are primary evidence of what users said, not independent verification that their claims are true.
• Do not access private or restricted content, collect unnecessary sensitive personal data, or redistribute downloaded media without the required rights. Follow applicable law and each platform's terms and access rules.
• The workflow cannot bypass platform verification or repair an expired login without user action.
• This catalog workflow intentionally excludes Jev Social's automatic onboarding and socai installer; missing prerequisites must be configured separately from a reviewed, pinned source.

Skill page

Conflict

Both copies describe the same Jev Social workflow (status check, bounded search, evidence extraction) and share the same pinned commit and core parameters. However, they disagree on how to handle missing setup: the davepoon copy permits running the pinned onboarding command with --skip-install if the user requests setup, while the sickn33 copy explicitly forbids running the catalog's onboarding/installer and requires the user to install socai separately. The sickn33 copy also adds a specific constraint that generic TikTok research must not expose media-download actions unless explicitly requested, which is absent from the davepoon copy. Because these are material procedural differences and a safety conflict, crowning one would hide a real alternative.