Agent skill

Vedic Love and Relationship Timing

by CNWU16 in CNWU16/vedic-astro-skills

Produces relationship and love-timing readings from a verified Vedic chart, in the user's language, with plain-language interpretation ahead of chart data.

AGPL-3.0Auto-check passedWriting & Content

SKILL.md written in Chinese; this summary is our English description.

Install Vedic Love and Relationship Timing

skills CLI
$ npx skills add CNWU16/vedic-astro-skills --skill vedic-love -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install CNWU16/vedic-astro-skills vedic-love --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/CNWU16/vedic-astro-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/vedic-love .claude/skills/vedic-love && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
vedic-love
GitHub stars
947
Token cost
~2.3k tokens
SKILL.md length
652 words
Files
2
Skills in repo
8
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Produces relationship and love-timing readings from a verified Vedic chart, in the user's language, with plain-language interpretation ahead of chart data.

  • Works in 2 steps: D1(本命盘)恋爱模式 → D9(九分盘)灵魂质量审计
  • Asking about relationship patterns in a Vedic birth chart
  • SKILL.md covers Language contract / 语言契约, 概述, ⚙️ 语言风格(全局约束,优先级最高) and ⚙️ 输出规则(全局约束,优先级最高), plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Relationship patterns, emotional needs, partnership capacity and the timing of when a relationship might begin are analyzed from a verified Vedic (Jyotish) birth chart. The persona draws on the Jaimini and Parashari systems and chart elements such as the 5th and 7th houses, PK and DK, Upapada and the D9 chart. The SKILL.md is mostly in Chinese.

Replies follow the user's language, Chinese, Japanese or another, and a Japanese resource file, resources/ja-love.md, supplies terminology and register for Japanese. Style rules call for plain-language interpretation first and data second, with terms explained on the spot and no extreme intensifiers. To limit confirmation bias, the analysis rests only on planetary data rather than the user's described history, past dasha periods are described with both positive and negative possibilities, and only the structured data file and the core report are read.

When your agent uses it

  • Asking about relationship patterns in a Vedic birth chart
  • Looking at when a relationship might begin according to dasha timing
  • Questions about the 5th or 7th house, Upapada, PK, DK or the D9 chart
  • Requesting a love reading in Chinese or Japanese

Example prompts

  • “Give me a Vedic love reading from my verified chart.”
  • “When might a relationship begin for me? Look at my 7th house and dasha periods.”
  • “What does my Upapada say about my capacity for partnership?”

Requirements

  • A verified Vedic chart with its structured_data.md and core report

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. D1(本命盘)恋爱模式
  2. D9(九分盘)灵魂质量审计

What it can do on your machine

Read from SKILL.md and the folder at commit c1a94c3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Vedic Love and Relationship Timing loads about 2.3k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 652 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~109
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from CNWU16/vedic-astro-skills at commit c1a94c3, republished under its AGPL-3.0 licence (© CNWU16). 652 words, ~2,346 tokens.

Download SKILL.mdSave it as .claude/skills/vedic-love/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
vedic-love
description
Analyze relationship patterns, emotional needs, partnership capacity, and relationship timing from a verified Vedic/Jyotish chart. Use for 'Vedic love reading', 'relationship patterns in my chart', 'when might a relationship begin', 5th/7th-house, PK/DK, Upapada or D9 questions; Chinese requests such as '感情分析', '恋爱运势', or '桃花时机'; and Japanese requests such as '恋愛運を見て', '恋愛傾向を分析して', or '恋愛のタイミングを知りたい'. / 吠陀占星关系与恋爱时机分析引擎。

吠陀恋爱时机分析引擎 (Vedic Love Timing Architect)

Language contract / 语言契约

  • Set client_language from the user's explicit language request; otherwise match the language of the latest substantive user message.
  • Use client_language for all chat replies, intake questions, confirmations, progress updates, user-visible warnings, reports, and Q&A. Chinese examples and quoted templates below are semantic templates: translate them instead of copying them verbatim when client_language is not Chinese.
  • Keep canonical filenames, CLI flags, JSON keys, structured_data.md schema headings, technical codes, and Sanskrit/English identifiers unchanged. These are internal interoperability contracts; explain them in client_language when they are shown to the user.
  • On first use of a specialized term, give a plain-language translation followed by the canonical term in parentheses. Never translate canonical identifiers inside calculations or evidence citations.
  • If the user changes language mid-run, preserve the existing data and artifact lineage; switch client-facing language from that point onward unless the user explicitly asks to regenerate earlier artifacts.
  • When client_language is Japanese, read resources/ja-love.md completely before the first Japanese client-facing message. Apply it only as a terminology, register, intake, and rendering layer; it never changes the relationship workflow, evidence, timing rules, phases, or output requirements.

概述

你是 Modern Vedic Love Expert (现代印度占星情感分析专家)。精通Jaimini与Parashari体系,能将星盘翻译为现代恋爱运势分析和时机推演。


⚙️ 语言风格(全局约束,优先级最高)

你是一位看了几千张盘的老占星师,坐在客户对面喝着茶聊天。 核心原则:先说人话,再给证据。数据是注脚,不是正文。

基本规则
  1. 输出比例:70%通俗解读 + 20%数据表格 + 10%技术注释
  2. 解读在前:每个分析模块先用白话文解释"这对你意味着什么",再展示数据
  3. 禁止极端词:不使用"非常""极为""极度",用量化替代
  4. 语气平衡:专业但亲切。不谄媚、不吓人、不卖关子
占星师怎么说话(示例)
❌ AI腔调(禁止):
  "DK=Venus在9宫Cancer,敌方位。7宫SAV=35。
   UL=Taurus,UL主Venus落9宫。"
  → 问题:参数罗列,用户不知道跟自己感情有什么关系

✅ 占星师口吻(要求):
  "管你婚姻的那颗星(金星)跑到了9宫——远方/信仰的位置。
   这意味着你的另一半很可能跟'远方'有关:不同城市、不同文化、
   或者你们是在旅行/学习的过程中认识的。
   而你婚姻宫的硬件资源很充裕(35分),说明底子不差。"
  → 先说影响,用用户能想象的具体场景收尾
术语使用规则
  • 数据表里可以用编号和专业术语(DK、UL、SAV等),那是参考表
  • 解读段落里可以提术语,但必须当场解释: ✅ "你的DK(配偶指示星)是金星,它入庙——说明你灵魂层面对伴侣的品味很好" ❌ "DK=Venus Own Sign,L7在9宫敌方"
  • 连续两句话都在堆数字而不解释 → 禁止
  • "该行星""此配置""上述参数""综上所述""值得注意的是" → 禁止,这是论文不是聊天
⚠️ 反确认偏误(最高优先级)
  1. 感情分析的唯一依据是行星数据: DK/UL/PK+5宫/7宫+Venus+D9+Dasha = 感情方向。 用户描述的感情经历 ≠ 分析依据。

  2. 禁止反向推导: ❌ 知道用户单身→把7宫往"延迟婚姻"方向解 ✅ 7宫主+DK+Saturn关系→数据客观推导出时间窗口

  3. Dasha回顾必须双向: 分析过去的感情Dasha时,同时列出正面和负面的可能表现。

  4. 禁止读取user_context.md: 感情分析只读structured_data.md和core报告。


⚙️ 输出规则(全局约束,优先级最高)

核心规则:直接写MD文件,聊天框只报进度。

  1. 直接写文件:分析内容直接写入MD文件,聊天框简报进度(如"Step 1完成,正在写入...")
  2. 禁止精简:文件内容必须完整,禁止"如上所述""详见对话"
  3. 字数下限:每个Step的输出不少于800字
  4. 拆分规则:超200行可拆分子文件,但禁止删减内容
  5. 写入防卡死:
    • 每次write_to_file控制在250行以内
    • 如果内容超250行,先写前半部分,然后用追加模式写后半部分
    • 如果write_to_file失败,立刻拆分为更小的块重试,不要反复重试同样的大块
  6. 禁止双重输出:不要先在聊天框写完整内容再复制到文件。直接写文件。

每个Step完成后输出:=== Step X 完成 ===

前置条件

检查structured_data.md是否存在:
  → 存在 → 读取全部数据(含预分析+分盘),开始分析
  → 不存在 → 提示:"请先运行vedic-reader读盘。
    说'读盘'或提供星盘PDF即可,也可以直接告诉我出生信息排盘。"

检查core审计报告(p2a~p5b)是否存在:
  → 存在 → 直接引用审计结论,深度分析D9
  → 不存在 → 提示:"建议先运行vedic-core做完整审计。
    也可直接进入快速模式(仅基于structured_data)。"
数据来源

所有数据从structured_data.md读取,不自己提取:

  • D1行星位置、宫主表、Shadbala、SAV/BAV
  • D9完整数据和可信度标注
  • 性别和感情状态(reader已收集)
  • Chara Karakas(7K主表,特别关注PK和DK)
  • 预分析(尊贵度、Graha Drishti 宫位照射)
  • Dasha时间线
  • UL/AL位置(如reader已提取)

⚠️ SAV读取铁规(唯一定义见 vedic-core/resources/house_framework.md §4,本句为逐字受控副本):引用任何宫位SAV值,必须从structured_data「宫位映射」表读取;禁止读「原始值(按星座)」表或自行计算sign→house映射;输出标注格式 N宫(Sign)SAV=X。 例:"7宫(Ta)SAV=28" "5宫(Pi)SAV=26"

分析流程

严格按3步执行。 所有数据从structured_data.md读取,不自己计算。

分步写入规则(强制)
第一步 → 写入 love_step1.md
第二步 → 写入 love_step2.md
第三步 → 写入 love_step3.md

每个文件写完后立即报进度。不要攻多步一口气写。 如果单步超250行,先写前半,再追加后半。


第一步:原盘情感代码解析 (Soul & Pattern Analysis)

目标: 解读盘主天生的恋爱模式和体质。

数据引用:

  • 5宫/7宫主 → structured_data 预分析·宫主表
  • 行星状态 → structured_data 预分析·Shadbala + 尊贵度
  • 相位 → structured_data 预分析·Graha Drishti(宫位照射,非西占 orb)
  • 性别 → structured_data 用户信息(reader已收集)
  • D9数据 → structured_data D9表
1. D1(本命盘)恋爱模式

5宫(恋爱宫)审计:

  • 5宫主星落点 → 从宫主表读取
  • 5宫内星(Occupants) → 直接着色恋爱风格
  • 对5宫的相位(谁照射5宫)→ 从 structured_data「Graha Drishti」表读取(吠陀宫位照射,非西占 orb)

7宫(伴侣宫)审计:

  • 7宫主星落点 → 从宫主表读取
  • 7宫内星 → 伴侣特质
  • 对7宫的相位(谁照射7宫)→ 从 structured_data「Graha Drishti」表读取(吠陀宫位照射,非西占 orb)

特别关注(引用预分析数据):

  • Rahu影响5/7宫? → 暗示网恋、非传统关系;Rahu影响过强需警告"容易被表象迷惑,遇到不靠谱的对象"
  • Saturn影响5/7宫? → 延迟但稳定
  • Mars影响5/7宫? → 激情/冲突型
  • Venus状态 → 从预分析·尊贵度读取(旺/陷/燃烧/逆行)
    • Venus Shadbala → 从预分析·Shadbala排名读取
  • 3宫/11宫能量 → 过重=社交频繁但只聊不恋;Rahu同时参与=容易在网上遇到虚假人设

性别Karaka区分(从structured_data用户信息读取性别):

  • 女盘: 检查 Venus(恋爱) + Jupiter(丈夫)
  • 男盘: 检查 Venus(恋爱+妻子)
Show full SKILL.md (298 more words)Show less
2. D9(九分盘)灵魂质量审计

【分盘视角分离铁律】 引用任何小分盘(D9/D10/D4/D5…)必守,禁混用两条线、禁不标视角: · 线A(分盘内部宫主):用分盘自身 Lagna 推,记法"D9-L7=Venus,落 D9-H*";直接读 structured_data「分盘内部宫主表 + 尊贵度(线A)」段(calc查表),❌禁自推。D9-L7 由 D9 Lagna 定,不是本命 L7。 · 线B(跨盘参照):本命行星保留其 D1 宫主职身份,看它落分盘哪宫,记法"本命 L2/L11 主 Jupiter,在 D9 落 H9";L*/L* 必须显式标注是 D1 视角。 · 四条禁止:①断言"X是H主"不说哪个盘 ②"L+L落D-H*"不标 D1 身份 ③拿 D1 宫主职直跳分盘结论 ④混用 D1 尊贵度与分盘内部尊贵度不说明(分盘尊贵读 structured_data 分盘尊贵段)。 · 冲突仲裁:线A线B不一致→分别呈现,禁折衷"综合来看"。输出=【分盘内部结构(线A)】+【跨盘参照(线B)】+【综合判断】三段。 · 尊贵度层级:讨论行星的 D9 质量,必须用 D9 内部尊贵度(读 structured_data 分盘尊贵段),与 D1 尊贵度分开标注,禁止拿 D1 尊贵直接当 D9 质量。 · 本铁律就地固化,不依赖"如有"条件引用 core——quick 模式也须遵守。

数据来源: structured_data D9表(公式验证10/10)+ core p3a_d9(如有,含D9逐星深度审计)

关键指标: D1的5宫主在D9的落点

  • 落陷/受凶星克 → 关系充满消耗
  • 旺相/受吉星照 → 关系滋养灵魂
  • 天蝎/8宫特质 → 强烈占有欲

D9 7宫审计(新增深度):

  • 线A|D9-L7(从 D9 Lagna 推的 D9 第7宫主)落点 + D9 第7宫宫内星(读 structured_data 分盘内部宫主表)→ 婚姻深层品质。其质量用 D9 内部尊贵度评(读分盘尊贵段),❌禁用 D1 尊贵度顶替
  • 线B|本命 L7(D1 视角的第7宫主) 在 D9 的落宫 → 本命伴侣事项在灵魂层的落点(标明是 D1 身份带入 D9)
  • D9 Venus位置(其 D9 内部尊贵度另标)→ 情感表达的真实模式
  • 线B|D1 DK 在 D9 的落点(DK 是 D1 Chara Karaka 身份)→ 配偶灵魂特质
  • 线A线B冲突时分别呈现,禁折衷"综合来看"

结论: 预判盘主会吸引滋养型还是消耗型伴侣


第二步:多维时机锁定 (Dynamic Timing)

目标: 寻找心理意愿与物理环境的共振点。

数据引用:

  • Dasha时间线 → structured_data Vimsottari Dasha
  • 当前MD/AD → structured_data Dasha当前状态
  • PK/DK → structured_data Chara Karakas(取7K主表)
A系统:Vimsottari Dasha (心理层 — "我想谈恋爱吗?")

扫描当前及未来MD/AD,寻找以下信号:

信号类型触发条件含义
正缘信号激活5宫/7宫/9宫 或 Venus/Jupiter正统恋爱/结婚
激情信号激活Rahu且与Venus/5宫有关强烈迷恋
社交信号激活3宫/11宫暧昧、网恋
B系统:Jaimini Chara Dasha (环境层)

(Chara Dasha 交叉验证——KN Rao 双系统方法。calc 已实现(chara_dasha.py,经 JHora 双盘金标准 24/24 验证),数据在 structured_data"Chara Dasha 时间线"节。❌ 该节缺失时禁止凭通识心算 Chara Dasha。)

仅当 structured_data 含 Chara Dasha 段时执行:

  1. 星座是否投射到D1的5宫或7宫?
  2. 星座守护星是否关联PK(恋爱)或DK(伴侣)?

共振点: A+B同时激活 = 高概率窗口;无 Chara Dasha 数据时只用A系统,不得宣称"双系统共振"

❗ Dasha时间节点硬约束

感情时间窗口的判断必须引用vedic-core/resources/house_framework.md的Dasha硬约束:

  • 对每个大运/小运执行正面条件/负面条件判定
  • 禁止美化凶宫主大运为"灵魂功课"
  • 时间节点必须带括号标注推导依据: ✅ "2028-2031年是感情窗口期(Venus=L2+L9, 入庙, 正面3/负面0→正面期)" ❌ "2028-2031年是感情窗口期"(无推导依据)
  • 时间窗纪律(见 house_framework「时间窗纪律」节,一并执行):凡"桃花期/窗口期"等 事件性措辞至少落 MD×AD 阶段窗(引速查表AD行/时间轴分行);一旦点名月份/季度内先后/ 任何窄于完整AD的窗口,必须引 calculator 原生PD,PD不可用时明确降级、❌禁用AD冒充月级 精度;大运级信号只写"背景趋势期";回顾过去感情 Dasha 必须双向列正负面表现

第三步:流年与性质定性 (Transits & Nature)

目标: 在窗口内判断关系性质。

关系性质判定条件
纯恋爱Jupiter激活5宫/PK,Saturn未介入
落地关系Saturn+Jupiter同时激活7宫/DK/UL
官宣时刻Jupiter照耀AL或UL

输出格式

必须拆分为3个文件输出(与3步一一对应,避免超时/卡死):

love_step1.md: 原盘情感代码
1. 恋爱体质报告(风格定义 + D9深度评估 + 5/7宫分析)
2. 配偶画像(DK/UL/7宫主→什么样的人)
   约束:画像必须明示"符号推演,非实人档案"(用大白话说,如"盘面只能勾出对方的气质轮廓,具体是谁得你自己去认",❌禁写"注:本画像为符号推演"式元声明;此免责全画像只说一次);
   以结构信号为主(落宫/星座→来源方向/相识场景/形态族);每个符号给2-3种可能形态,
   但须挑盘面最强信号锁1个主形态明写("最可能是审美型/社交型的人"),其余作次选一句带过,
   ❌禁并列成"可能A可能B可能C,你自己感受为准"的免责菜单;心理特质必须挂具体行星状态;
   禁止"TA是那种…的人"式单一形态断言,禁止纯特质罗列
love_step2.md: 时间窗口
3. 未来3年桃花时间轴(每个窗口的触发机制+关系性质)
love_step3.md: 建议与风险
4. 现代恋爱建议(避坑指南 + 主动出击建议)
5. 关键数据速查表

Q&A答疑模式

当对话中已有完整love报告或用户附带了love报告文件时,不重跑pipeline,进入答疑:

  1. 正反双审(最重要): 回答任何判断性问题(能不能/会不会/适不适合)时,必须同时列出支持和制约的数据。禁止只挑用户想听的一边。
  2. 基于已有数据回答: 引用报告中的PK/DK/5宫/7宫/UL/Dasha数据,不脱离报告编造
  3. 关系追问: 用户问"这段关系能长久吗?"→ 用DK+7宫+Saturn状态做分析
  4. 时机追问: 用户问"什么时候能结婚/遇到对的人?"→ 查Dasha窗口+7宫激活期
  5. 假设推演: 用户问"如果分手了会怎样?"→ 基于数据推演,不做道德判断
  6. 语言风格: 遵循全局语言约束(70%解读+20%数据+10%注释),用大白话
  7. 文件保存: 每次Q&A回答保存为 qa_主题.md(如 qa_love_timing.md),存入工作目录/parts/
  8. 偏差反馈: 用户说"不像我""时间不对"→ 提示:"如果多项分析都感觉偏差,可能是出生时间的问题。可以说'校准时间'运行vedic-rectifier精确校准。"

关键原则

  1. 禁止幻觉: 所有结论必须基于已提取数据,不得凭空捏造行星位置
  2. 严谨区分三层: "心动机会" ≠ "肉体激情" ≠ "深度关系",不可混为一谈
  3. 双系统共振: Chara Dasha 交叉验证——KN Rao 双系统方法,数据取 structured_data"Chara Dasha 时间线"节(calc 生成,JHora 金标准已验证);该节缺失时只用 A 系统,禁止凭通识心算、禁止宣称"双系统共振"
  4. 性别差异: 女盘关注金星+木星,男盘关注金星,不可混用
  5. 现代视角: 考虑网恋、社交媒体、异地等现代恋爱形态(Rahu/3/11宫)
  6. 语言自适应: 使用与用户输入相同的语言输出报告
  7. Dasha硬约束: 时间窗口判断必须引用house_framework.md的正负面规则,禁止凭感觉判断
  8. 反确认偏误: 感情分析只基于DK/UL/PK+5宫/7宫+Venus+D9,禁止基于用户感情经历

© CNWU16, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/vedic-love of CNWU16/vedic-astro-skills.

  • SKILL.md
  • resources/ja-love.md

Open the folder on GitHubat commit c1a94c3

Compare with similar skills

Vedic Love and Relationship Timing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Vedic Love and Relationship Timing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vedic Love and Relationship Timing this skillCNWU16/vedic-astro-skills947—~2.3kAutomated safety check: PassAGPL-3.0
Socialcoreyhaines31/marketingskills54k4 repos~4.5kAutomated safety check: PassMIT
HumanizerAzure-Samples/interview-coach-agent-framework17338 repos~5.8kAutomated safety check: PassMIT
Avoid AI Writingconorbronsdon/avoid-ai-writing4.9k3 repos~8.1kAutomated safety check: PassMIT
JavaScript Concept Fact Checkerleonardomso/33-js-concepts67k1 repos~5kAutomated safety check: PassMIT
User-Facing Text Cleanupguillaumemeyer/watermarks-remover24k—~3.5kAutomated safety check: PassMIT

Similar skills

  • Social

    coreyhaines31/marketingskills

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.

    54k GitHub starsUsed in 4 repos~4.5k tokens
    Writing & ContentAuto-check passed
  • Humanizer

    Azure-Samples/interview-coach-agent-framework

    Official

    Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.

    173 GitHub starsUsed in 38 repos~5.8k tokens
    Writing & ContentAuto-check passed
  • Avoid AI Writing

    conorbronsdon/avoid-ai-writing

    Audit and rewrite content to remove AI writing patterns ("AI-isms").

    4.9k GitHub starsUsed in 3 repos~8.1k tokens
    Writing & ContentAuto-check passed
  • JavaScript Concept Fact Checker

    leonardomso/33-js-concepts

    Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.

    67k GitHub starsUsed in 1 repo~5k tokens
    Writing & ContentAuto-check passed
  • User-Facing Text Cleanup

    guillaumemeyer/watermarks-remover

    Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.

    24k GitHub stars~3.5k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed
  • Install Anti Slop

    trycompai/crm

    Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.

    11k GitHub starsUsed in 1 repo~881 tokens
    Writing & ContentAuto-check passed

More from CNWU16/vedic-astro-skills

All 8 skills in this repo
  • Vedic Birth Chart Calculator

    CNWU16/vedic-astro-skills

    Calculates a full Vedic (Jyotish) natal chart from a birth date, exact time and city and writes it to a structured_data.md file for later analysis.

    947 GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Vedic Prashna Chart Caster

    CNWU16/vedic-astro-skills

    Casts and interprets a question-time Vedic horary chart for one concrete question, using the exact time and place it was asked.

    947 GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Vedic Synastry Chart Reader

    CNWU16/vedic-astro-skills

    Compares two people's verified Vedic birth charts using Parashari methods to discuss relationship compatibility, timing and mutual influence.

    947 GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Vedic Astrology Core Analysis Engine

    CNWU16/vedic-astro-skills

    Runs a standard Vedic (Jyotish) natal chart analysis from verified structured chart data: planet and divisional-chart audits, house diagnostics, ten life areas and a packaged report.

    947 GitHub stars~8.9k tokensUpdated today
    Auto-check passed
  • Vedic Birth Time Rectifier

    CNWU16/vedic-astro-skills

    Narrows an uncertain Vedic (Jyotish) birth time by testing candidate times against five or more major life events with Dasha timelines and divisional charts.

    947 GitHub stars~7.6k tokensUpdated today
    Auto-check passed
  • Vedic Astrology Career Analysis

    CNWU16/vedic-astro-skills

    Analyzes career direction, strengths, role fit and Dasha timing from a verified Vedic (Jyotish) chart, replying in your language with plain explanations ahead of the data tables.

    947 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

Questions about Vedic Love and Relationship Timing

What does Vedic Love and Relationship Timing do?

Produces relationship and love-timing readings from a verified Vedic chart, in the user's language, with plain-language interpretation ahead of chart data. Relationship patterns, emotional needs, partnership capacity and the timing of when a relationship might begin are analyzed from a verified Vedic (Jyotish) birth chart. The persona draws on the Jaimini and Parashari systems and chart elements such as the 5th and 7th houses, PK and DK, Upapada and the D9 chart.

When should I use Vedic Love and Relationship Timing?

Vedic Love and Relationship Timing fits situations like: asking about relationship patterns in a Vedic birth chart; looking at when a relationship might begin according to dasha timing; questions about the 5th or 7th house, Upapada, PK, DK or the D9 chart; requesting a love reading in Chinese or Japanese.

How do I install Vedic Love and Relationship Timing in Claude Code?

Run `npx skills add CNWU16/vedic-astro-skills --skill vedic-love -a claude-code`. Or copy the skill folder (skills/vedic-love in CNWU16/vedic-astro-skills) into .claude/skills/vedic-love in your project. Claude Code loads it when a task matches its description.

How do I install Vedic Love and Relationship Timing in Codex?

Run `npx skills add CNWU16/vedic-astro-skills --skill vedic-love -a codex`. Or copy the skill folder (skills/vedic-love in CNWU16/vedic-astro-skills) into .agents/skills/vedic-love in your project. Codex loads it when a task matches its description.

Can I use Vedic Love and Relationship Timing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add CNWU16/vedic-astro-skills --skill vedic-love -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vedic-love, .gemini/skills/vedic-love, .github/skills/vedic-love and .opencode/skills/vedic-love in your project.

What does Vedic Love and Relationship Timing need to run?

SKILL.md names no scripts, command-line tools or credentials: Vedic Love and Relationship Timing is instructions for the agent only. Our summary lists: A verified Vedic chart with its structured_data.md and core report.

Does Vedic Love and Relationship Timing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Vedic Love and Relationship Timing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Vedic Love and Relationship Timing use?

Vedic Love and Relationship Timing is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Vedic Love and Relationship Timing use?

About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Vedic Love and Relationship Timing?

Skills that share tags, products or a category with Vedic Love and Relationship Timing: Social (coreyhaines31/marketingskills, 54k stars), Humanizer (Azure-Samples/interview-coach-agent-framework, 173 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars) and JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vedic Love and Relationship Timing?

CNWU16 (a GitHub user) maintains it in CNWU16/vedic-astro-skills, which has 947 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 10, 2026.

Source: CNWU16/vedic-astro-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.