personal-strategic-signal-intelligence
Turn an executive or operator's private reading, highlights, notes, social bookmarks, and applied work into source-grounded decision intelligence
Install / Use
npx skills add ericosiu/ai-marketing-skills --skill personal-strategic-signal-intelligenceInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of personal-strategic-signal-intelligence
personal-strategic-signal-intelligence scores 95/100 on our quality scale, 371st of 4,700 Development & Engineering skills we index (top 8%).
Its SKILL.md is 22 KB long, well organised into 46 sections with 5 code examples: a thorough specification that gives an agent plenty to work with.
With 3,573 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so personal-strategic-signal-intelligence is actively maintained.
- Our last check on 2026-11-16 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-06. Automated pattern scan on 2026-10-06. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
personal-strategic-signal-intelligence compared with similar skills
All 4 of these similar skills score higher than personal-strategic-signal-intelligence; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| personal-strategic-signal-intelligence (this skill)by ericosiu | 95 | 3.6k | 55d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install personal-strategic-signal-intelligence?
- Run
npx skills add ericosiu/ai-marketing-skills --skill personal-strategic-signal-intelligence. The install tabs above show the steps for each supported agent. - Which AI agents does personal-strategic-signal-intelligence work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is personal-strategic-signal-intelligence safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is personal-strategic-signal-intelligence still maintained?
- The repository was last updated about 2 months ago, so personal-strategic-signal-intelligence is actively maintained.
Skill content
View source on GitHubname: personal-strategic-signal-intelligence description: Turn an executive or operator's private reading, highlights, notes, social bookmarks, and applied work into source-grounded decision intelligence. Use when detecting attention drift, surfacing pre-decision signals, testing contradictions, converting bookmarks into builds, recombining founder IP, finding service-offer arbitrage, or mapping content negative space.
Personal Strategic Signal Intelligence
Overview
Personal Strategic Signal Intelligence (PSSI) converts a person's accumulated information trail into decision support. It is not a content-idea generator with a bookmark import attached. Its first job is to clarify what the operator is noticing, testing, doubting, and becoming ready to decide. Content, products, offers, and experiments are downstream applications.
The system may read from multiple personal-signal sources, including:
- read-later libraries
- browser or knowledge-base saves
- social bookmarks
- explicitly completed reads
- highlights and annotations
- personal notes and memos
- meeting follow-ups and decision records
- experiments, prototypes, and shipped applications
- user-supplied public writing or prior decisions
Treat every source as evidence with a known strength, date, and lineage. Never present an inferred belief as a declared fact.
When to Use
Use this skill when the user asks to:
- understand how their attention or strategic interests are changing
- identify decisions they appear to be approaching
- compare stated beliefs with recent evidence or behavior
- turn saved material into an experiment, prototype, or operating change
- recombine existing frameworks into defensible founder or executive IP
- discover offers or services implied by recurring market pain
- find important topics they study but have not addressed publicly
- run a weekly personal intelligence review
- trigger a focused review after a major decision, cluster of saves, contradiction, or applied experiment
Do not use it to:
- diagnose personality, mental health, or private motives
- summarize an entire archive without a decision question
- rank people, clients, or employees from private activity
- publish inferred beliefs or sensitive source material
- treat bookmarks, likes, or follows as endorsements
- create an arbitrary high-frequency synthesis loop
Operating Principles
1. Decision intelligence before content
Always ask what decision, allocation, belief update, risk, or experiment the signal may inform. Only after that should the system propose content. If no decision relevance is found, label the output as exploratory rather than forcing a business implication.
2. Attention is not conviction
A save is evidence of attention, not agreement. Repeated saves can indicate curiosity, anxiety, active research, competitive monitoring, or disagreement.
Use this signal-strength ladder by default:
| Signal | Default interpretation | Relative strength | |---|---|---:| | Save, like, follow, or bookmark | Weak attention signal | 1 | | Repeat saves across time or sources | Sustained attention | 2 | | Explicitly marked as read | Deliberate exposure | 3 | | Highlight or annotation | Salient idea | 4 | | Original note or synthesis | Active interpretation | 5 | | Decision reference or stated belief | Expressed conviction | 6 | | Experiment, prototype, purchase, or operating change | Applied conviction | 7 | | Repeated application with measured outcome | Validated operating belief | 8 |
Weights are configurable. Never convert a weak signal into a strong claim merely because many weak signals exist.
3. Private inferred beliefs stay private
The system may infer candidate beliefs to help the user think. Each inference must be labeled private inferred belief, include supporting and contradicting evidence, and carry a confidence level. It must not be published, sent to collaborators, or treated as the user's stated position without explicit confirmation.
Use careful language:
- Good: "Your recent notes may indicate growing skepticism about broad automation."
- Bad: "You believe broad automation is a mistake."
4. Lineage before synthesis
Every material claim must link back to its source records. Preserve original source identifiers internally and show human-readable citations in outputs. If a claim cannot be traced, mark it unverified synthesis or remove it.
5. No recursive evidence
A prior synthesis is not new evidence. Do not cite a dashboard, weekly brief, generated note, or earlier model inference as independent support unless it contains new primary observations.
Maintain these rules:
- Primary evidence is a source item, explicit user statement, observed application, or measured outcome.
- Derived evidence is a summary, cluster label, score, or inference built from primary evidence.
- Derived evidence may help navigation but cannot increase confidence by being counted again.
- If a generated artifact is later annotated by the user, only the new annotation is primary evidence; the generated text remains derived.
- Keep a
derived_fromlist so cycles can be detected and rejected.
Source Contract
Normalize source records before analysis:
signal_id: stable-source-id
source_type: read_later | social_bookmark | highlight | note | decision | application | other
source_system: user-facing connector name
source_url: optional canonical URL
source_item_id: optional connector-native ID
captured_at: ISO-8601 timestamp
engaged_at: optional ISO-8601 timestamp
engagement: saved | opened | read | highlighted | annotated | applied | measured
text_excerpt: minimal relevant excerpt
user_text: optional user-authored note
privacy: private | shareable | public
content_hash: hash of normalized source content
Required lineage fields for every derived claim:
claim_id: stable-derived-id
claim: concise statement
claim_type: observation | private_inferred_belief | hypothesis | recommendation
source_ids: [signal-id-1, signal-id-2]
derived_from: []
supporting_evidence: []
contradicting_evidence: []
confidence: low | medium | high
created_at: ISO-8601 timestamp
Reject claims with empty source_ids unless they are explicitly labeled as questions or hypotheses.
Analysis Workflow
Step 1: Establish scope and decision context
Capture:
- review window
- available source types
- current decision or strategic question, if any
- privacy boundary
- expected output: decision memo, contradiction brief, build queue, offer map, content map, or weekly review
If the user provides no decision question, begin with broad signal detection but do not manufacture urgency.
Step 2: Ingest minimally
Request only fields required for the chosen module. Prefer incremental syncs over full-library exports. Store connector tokens outside notes, prompts, and generated artifacts. Do not include full private documents when a source ID, title, and relevant excerpt are enough.
Step 3: Normalize and deduplicate
Deduplicate by canonical URL, native source ID, and content hash. Preserve multiple engagement events as events on one source rather than pretending they are independent sources. Record edits and deletions when the connector exposes them.
Step 4: Score evidence
Score along separate dimensions:
attention_strength: frequency, recency, diversity of sourcesconviction_strength: notes, decisions, application, measured outcomessource_quality: primary evidence, specificity, credibilitystrategic_relevance: connection to active decisions or stated prioritiesnovelty: difference from already-known themescontradiction: tension with prior statements or behavior
Never combine attention and conviction into one opaque score. A theme may have high attention and low conviction.
Step 5: Build claims with counter-evidence
For each high-value cluster:
- State the observable pattern.
- List primary evidence.
- List plausible alternative explanations.
- Search for contradicting evidence.
- Write any belief inference as private and provisional.
- Identify the decision, test, or question it informs.
- Set confidence based on evidence quality, not rhetorical coherence.
Step 6: Apply the expert panel
Use a configurable panel and pass threshold. The default pass threshold is 90/100. The user may set a different threshold for exploratory work, but the chosen threshold must appear in the output.
Recommended panel lenses:
| Lens | Question | |---|---| | Evidence auditor | Are claims traceable to primary evidence without double counting? | | Decision strategist | Does this materially improve a real decision? | | Contrarian reviewer | What evidence or interpretation would reverse the conclusion? | | Operator | Is there a concrete, bounded next action? | | Privacy steward | Is the output safe for its intended audience? | | Domain expert | Is the analysis credible in the relevant field? | | Measurement reviewer | Can the recommendation produce observable feedback? |
Score each lens from 0-100, average the scores, and record both the average and threshold. A sub-90 item may still be kept as an exploratory hypothesis, but it must not be promoted as a recommendation under the default configuration.
Step 7: Produce an action artifact
Every promoted insight should end in one of:
- a decision question with options and evidence
- a falsifiable experiment
- a small build specification
- a contradiction to resolve
- an offer hypothesis to validate
- a content gap with a source-grounded point of view
- a monitored theme with a clear trigger for re-review
Step 8: Record feedback
Capture what the user accepted, rejected, corrected, applied, or measured. User corrections become new primary evidence. Model restatements do not.
Seven Capability Modules
Module 1: Attention Drift
Purpose: Detect how the operator's attention is changing without confusing attention with belief.
Compare windows by theme, source diversity, recurrence, and engagement depth. Report:
- emerging themes
- accelerating themes
- fading themes
- persistent themes
- themes moving from saves to notes or application
- themes with high attention but no evidence of conviction
Prefer proportions and directional language over exact corpus totals when sharing outside the private workspace.
Module 2: Pre-Decision Oracle
Purpose: Surface decisions the operator may be approaching before they are explicitly framed.
Look for converging signals such as repeated research, opposing viewpoints, implementation notes, vendor comparisons, and applied tests. Output candidate decisions as questions, not predictions:
## Candidate decision
**Question:** Should we standardize this workflow now or keep it experimental?
**Why it may be approaching:** <source-grounded pattern>
**Evidence for acting:** <citations>
**Evidence for waiting:** <citations>
**Smallest reversible test:** <action>
**Confidence:** medium
Do not claim to know what the user will decide.
Module 3: Contradiction / Decision Court
Purpose: Make productive contradictions visible and force competing hypotheses to face the same evidence.
Use this configurable hybrid entry policy by default:
- Explicit, in-scope decisions enter automatically. When the user clearly marks an in-scope item as a decision, add it to Decision Court without requiring a separate nomination approval.
- Inferred in-scope candidates require approval. When the system infers that a potentially high-stakes decision is emerging, nominate it with a short source-grounded rationale and wait for the user's approval before running the full Decision Court analysis.
- Ordinary activity is not a decision. Do not treat routine conversations, questions, tasks, notes, or to-dos as decisions merely because they may have strategic relevance.
Use this sanitized V0 scope unless the user configures another on
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
