viruagent-cli 0.3.0 → 0.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.ko.md +33 -24
- package/README.md +32 -23
- package/package.json +1 -1
- package/skills/viruagent.md +33 -13
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2025 greekr4
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
package/README.ko.md
CHANGED
|
@@ -1,9 +1,21 @@
|
|
|
1
1
|
|
|
2
|
-
|
|
2
|
+
<p align="center">
|
|
3
|
+
<img src="https://github.com/user-attachments/assets/76be6d06-3f0d-44e5-8152-d64b2fc68894" alt="viruagent-cli" />
|
|
4
|
+
</p>
|
|
5
|
+
|
|
6
|
+
<h1 align="center">viruagent-cli</h1>
|
|
3
7
|
|
|
4
8
|
<p align="center">
|
|
5
|
-
<a href="
|
|
6
|
-
|
|
9
|
+
<a href="https://github.com/greekr4/viruagent-cli/stargazers"><img src="https://img.shields.io/github/stars/greekr4/viruagent-cli" alt="GitHub stars"></a>
|
|
10
|
+
</p>
|
|
11
|
+
<p align="center">
|
|
12
|
+
<a href="https://www.npmjs.com/package/viruagent-cli"><img src="https://img.shields.io/npm/v/viruagent-cli?color=blue" alt="npm version"></a>
|
|
13
|
+
<a href="LICENSE"><img src="https://img.shields.io/npm/l/viruagent-cli" alt="license"></a>
|
|
14
|
+
<a href="https://nodejs.org"><img src="https://img.shields.io/node/v/viruagent-cli" alt="node version"></a>
|
|
15
|
+
</p>
|
|
16
|
+
<p align="center">
|
|
17
|
+
<a href="README.md"><img src="https://img.shields.io/badge/English-blue" alt="English"></a>
|
|
18
|
+
<a href="README.ko.md"><img src="https://img.shields.io/badge/한국어-red" alt="Korean"></a>
|
|
7
19
|
</p>
|
|
8
20
|
|
|
9
21
|
**AI 에이전트가 블로그를 쓰고, 태그를 만들고, 발행까지 자동으로 처리하는 CLI 도구**
|
|
@@ -28,25 +40,25 @@
|
|
|
28
40
|
- **에이전트**: 스킬을 읽고 CLI를 조합하여 자율적으로 실행
|
|
29
41
|
- **커스텀**: 스킬 파일을 직접 수정하여 원하는 대로 동작하도록 설정 가능
|
|
30
42
|
|
|
31
|
-
##
|
|
43
|
+
## 빠른 시작
|
|
32
44
|
|
|
33
45
|

|
|
34
46
|
|
|
35
|
-
아래 내용을 AI 에이전트에게 그대로 복사해서 보여주세요.
|
|
47
|
+
아래 내용을 AI 에이전트에게 그대로 복사해서 보여주세요. (AI 에이전트 대상이므로 영어로 작성되어 있습니다)
|
|
36
48
|
|
|
37
49
|
```
|
|
38
50
|
You are installing viruagent-cli, a blog publishing CLI tool. Follow these steps in order.
|
|
39
51
|
|
|
40
|
-
Step 1:
|
|
41
|
-
npx viruagent-cli --spec
|
|
42
|
-
If the output contains "ok": true, the CLI is ready. If it fails, check that Node.js
|
|
43
|
-
>= 18 is installed.
|
|
44
|
-
|
|
45
|
-
Step 2: Install skill
|
|
52
|
+
Step 1: Install skill
|
|
46
53
|
npx viruagent-cli install-skill
|
|
47
54
|
This copies the skill file to ~/.claude/commands/viruagent.md. Confirm the file
|
|
48
55
|
exists before proceeding.
|
|
49
56
|
|
|
57
|
+
Step 2: Verify CLI
|
|
58
|
+
npx viruagent-cli --spec
|
|
59
|
+
If the output contains "ok": true, the CLI is ready. If it fails, check that Node.js
|
|
60
|
+
>= 18 is installed.
|
|
61
|
+
|
|
50
62
|
Tell the user that viruagent-cli installation is complete.
|
|
51
63
|
```
|
|
52
64
|
|
|
@@ -63,7 +75,8 @@ npx viruagent-cli login --from-chrome --profile "Profile 2"
|
|
|
63
75
|
npx viruagent-cli login --username <id> --password <pw> --headless
|
|
64
76
|
```
|
|
65
77
|
|
|
66
|
-
|
|
78
|
+
> [!TIP]
|
|
79
|
+
> `--from-chrome`은 macOS Keychain을 통해 Chrome 쿠키 DB를 직접 복호화합니다. 브라우저 실행 없이, 2FA 없이, 1초 내 완료됩니다.
|
|
67
80
|
|
|
68
81
|
## 사용법
|
|
69
82
|
|
|
@@ -93,14 +106,14 @@ npx viruagent-cli login --username <id> --password <pw> --headless
|
|
|
93
106
|
|
|
94
107
|
## 기술 스택
|
|
95
108
|
|
|
96
|
-
| 영역 | 기술 |
|
|
97
|
-
| --- | --- |
|
|
98
|
-
| CLI 프레임워크 | Commander.js |
|
|
99
|
-
| 브라우저 자동화 | Playwright (Chromium) |
|
|
100
|
-
| 쿠키 복호화 | macOS Keychain + AES-128-CBC |
|
|
101
|
-
| 세션 관리 | JSON 파일 (`~/.viruagent-cli/`) |
|
|
102
|
-
| 이미지 검색 | DuckDuckGo, Wikimedia, Commons |
|
|
103
|
-
| 출력 형식 | JSON envelope
|
|
109
|
+
| 영역 | 기술 |
|
|
110
|
+
| --- | --- |
|
|
111
|
+
| CLI 프레임워크 | Commander.js |
|
|
112
|
+
| 브라우저 자동화 | Playwright (Chromium) |
|
|
113
|
+
| 쿠키 복호화 | macOS Keychain + AES-128-CBC |
|
|
114
|
+
| 세션 관리 | JSON 파일 (`~/.viruagent-cli/`) |
|
|
115
|
+
| 이미지 검색 | DuckDuckGo, Wikimedia, Commons |
|
|
116
|
+
| 출력 형식 | JSON envelope (`{ ok, data }` / `{ ok, error, hint }`) |
|
|
104
117
|
|
|
105
118
|
## Contributing
|
|
106
119
|
|
|
@@ -116,7 +129,3 @@ git checkout -b feature/my-feature
|
|
|
116
129
|
git commit -m "[FEAT] Add my feature"
|
|
117
130
|
git push origin feature/my-feature
|
|
118
131
|
```
|
|
119
|
-
|
|
120
|
-
## License
|
|
121
|
-
|
|
122
|
-
MIT
|
package/README.md
CHANGED
|
@@ -1,9 +1,21 @@
|
|
|
1
1
|
|
|
2
|
-
|
|
2
|
+
<p align="center">
|
|
3
|
+
<img src="https://github.com/user-attachments/assets/76be6d06-3f0d-44e5-8152-d64b2fc68894" alt="viruagent-cli" />
|
|
4
|
+
</p>
|
|
5
|
+
|
|
6
|
+
<h1 align="center">viruagent-cli</h1>
|
|
3
7
|
|
|
4
8
|
<p align="center">
|
|
5
|
-
<a href="
|
|
6
|
-
|
|
9
|
+
<a href="https://github.com/greekr4/viruagent-cli/stargazers"><img src="https://img.shields.io/github/stars/greekr4/viruagent-cli" alt="GitHub stars"></a>
|
|
10
|
+
</p>
|
|
11
|
+
<p align="center">
|
|
12
|
+
<a href="https://www.npmjs.com/package/viruagent-cli"><img src="https://img.shields.io/npm/v/viruagent-cli?color=blue" alt="npm version"></a>
|
|
13
|
+
<a href="LICENSE"><img src="https://img.shields.io/npm/l/viruagent-cli" alt="license"></a>
|
|
14
|
+
<a href="https://nodejs.org"><img src="https://img.shields.io/node/v/viruagent-cli" alt="node version"></a>
|
|
15
|
+
</p>
|
|
16
|
+
<p align="center">
|
|
17
|
+
<a href="README.md"><img src="https://img.shields.io/badge/English-blue" alt="English"></a>
|
|
18
|
+
<a href="README.ko.md"><img src="https://img.shields.io/badge/한국어-red" alt="Korean"></a>
|
|
7
19
|
</p>
|
|
8
20
|
|
|
9
21
|
**A CLI tool where AI agents write, tag, and publish blog posts automatically.**
|
|
@@ -28,7 +40,7 @@ User: /viruagent "Write a post"
|
|
|
28
40
|
- **Agent**: Reads the skill and orchestrates CLI commands autonomously
|
|
29
41
|
- **Custom**: Edit the skill file to customize behavior
|
|
30
42
|
|
|
31
|
-
##
|
|
43
|
+
## Quick Start
|
|
32
44
|
|
|
33
45
|

|
|
34
46
|
|
|
@@ -37,16 +49,16 @@ Copy the following to your AI agent:
|
|
|
37
49
|
```
|
|
38
50
|
You are installing viruagent-cli, a blog publishing CLI tool. Follow these steps in order.
|
|
39
51
|
|
|
40
|
-
Step 1:
|
|
41
|
-
npx viruagent-cli --spec
|
|
42
|
-
If the output contains "ok": true, the CLI is ready. If it fails, check that Node.js
|
|
43
|
-
>= 18 is installed.
|
|
44
|
-
|
|
45
|
-
Step 2: Install skill
|
|
52
|
+
Step 1: Install skill
|
|
46
53
|
npx viruagent-cli install-skill
|
|
47
54
|
This copies the skill file to ~/.claude/commands/viruagent.md. Confirm the file
|
|
48
55
|
exists before proceeding.
|
|
49
56
|
|
|
57
|
+
Step 2: Verify CLI
|
|
58
|
+
npx viruagent-cli --spec
|
|
59
|
+
If the output contains "ok": true, the CLI is ready. If it fails, check that Node.js
|
|
60
|
+
>= 18 is installed.
|
|
61
|
+
|
|
50
62
|
Tell the user that viruagent-cli installation is complete.
|
|
51
63
|
```
|
|
52
64
|
|
|
@@ -63,7 +75,8 @@ npx viruagent-cli login --from-chrome --profile "Profile 2"
|
|
|
63
75
|
npx viruagent-cli login --username <id> --password <pw> --headless
|
|
64
76
|
```
|
|
65
77
|
|
|
66
|
-
|
|
78
|
+
> [!TIP]
|
|
79
|
+
> `--from-chrome` decrypts Chrome's cookie database directly via macOS Keychain. No browser launch, no 2FA — completes in under 1 second.
|
|
67
80
|
|
|
68
81
|
## Usage
|
|
69
82
|
|
|
@@ -93,14 +106,14 @@ Ask the agent for detailed usage or customization help.
|
|
|
93
106
|
|
|
94
107
|
## Tech Stack
|
|
95
108
|
|
|
96
|
-
| Area | Tech |
|
|
97
|
-
| --- | --- |
|
|
98
|
-
| CLI Framework | Commander.js |
|
|
99
|
-
| Browser Automation | Playwright (Chromium) |
|
|
100
|
-
| Cookie Decryption | macOS Keychain + AES-128-CBC |
|
|
101
|
-
| Session Management | JSON file (`~/.viruagent-cli/`) |
|
|
102
|
-
| Image Search | DuckDuckGo, Wikimedia, Commons |
|
|
103
|
-
| Output Format | JSON envelope
|
|
109
|
+
| Area | Tech |
|
|
110
|
+
| --- | --- |
|
|
111
|
+
| CLI Framework | Commander.js |
|
|
112
|
+
| Browser Automation | Playwright (Chromium) |
|
|
113
|
+
| Cookie Decryption | macOS Keychain + AES-128-CBC |
|
|
114
|
+
| Session Management | JSON file (`~/.viruagent-cli/`) |
|
|
115
|
+
| Image Search | DuckDuckGo, Wikimedia, Commons |
|
|
116
|
+
| Output Format | JSON envelope (`{ ok, data }` / `{ ok, error, hint }`) |
|
|
104
117
|
|
|
105
118
|
## Contributing
|
|
106
119
|
|
|
@@ -116,7 +129,3 @@ git checkout -b feature/my-feature
|
|
|
116
129
|
git commit -m "[FEAT] Add my feature"
|
|
117
130
|
git push origin feature/my-feature
|
|
118
131
|
```
|
|
119
|
-
|
|
120
|
-
## License
|
|
121
|
-
|
|
122
|
-
MIT
|
package/package.json
CHANGED
package/skills/viruagent.md
CHANGED
|
@@ -62,47 +62,67 @@ Every post must follow this structure. Write in the same language as the user's
|
|
|
62
62
|
|
|
63
63
|
```html
|
|
64
64
|
<!-- 1. Hook (blockquote style2 for topic quote) -->
|
|
65
|
-
<blockquote data-ke-style="style2">[One impactful sentence
|
|
65
|
+
<blockquote data-ke-style="style2">[One impactful sentence that captures the core insight or tension]</blockquote>
|
|
66
66
|
<p data-ke-size="size16"> </p>
|
|
67
67
|
|
|
68
|
-
<!-- 2. Introduction (
|
|
69
|
-
<p>[
|
|
68
|
+
<!-- 2. Introduction (2~3 paragraphs: context, reader empathy, what this post covers) -->
|
|
69
|
+
<p data-ke-size="size18">[Describe the situation the reader relates to — paint a vivid picture, 3~5 sentences]</p>
|
|
70
|
+
<p data-ke-size="size18">[Set expectations: what angle this post takes, what the reader will gain]</p>
|
|
70
71
|
<p data-ke-size="size16"> </p>
|
|
71
72
|
|
|
72
|
-
<!-- 3. Body (
|
|
73
|
+
<!-- 3. Body (3~4 sections with h2, each section has 2~3 paragraphs) -->
|
|
73
74
|
<!-- Use <p data-ke-size="size16"> </p> between sections for spacing -->
|
|
74
75
|
<h2>[Section 1 Title — keyword-rich]</h2>
|
|
75
|
-
<p>[
|
|
76
|
+
<p data-ke-size="size18">[Explain the concept or situation in 3~5 sentences. Include evidence: expert quotes, data, or real-world examples]</p>
|
|
77
|
+
<p data-ke-size="size18">[Deepen the point with analysis, comparison, or implication. Connect to the reader's experience]</p>
|
|
76
78
|
<ul>
|
|
79
|
+
<li>[Key point — only use lists for 3+ concrete items worth scanning]</li>
|
|
77
80
|
<li>[Key point]</li>
|
|
78
81
|
<li>[Key point]</li>
|
|
79
82
|
</ul>
|
|
83
|
+
<p data-ke-size="size16"> </p>
|
|
80
84
|
|
|
81
85
|
<h2>[Section 2 Title]</h2>
|
|
82
|
-
<p>[
|
|
86
|
+
<p data-ke-size="size18">[Introduce a new angle, case study, or supporting argument. 3~5 sentences with specific details]</p>
|
|
87
|
+
<p data-ke-size="size18">[Analyze why this matters. Use <strong>bold</strong> for key terms. Connect back to the main thesis]</p>
|
|
88
|
+
<p data-ke-size="size16"> </p>
|
|
89
|
+
|
|
90
|
+
<h2>[Section 3 Title]</h2>
|
|
91
|
+
<p data-ke-size="size18">[Practical application or actionable insight. Show, don't just tell]</p>
|
|
92
|
+
<p data-ke-size="size18">[Bridge to the conclusion — "what this all means"]</p>
|
|
93
|
+
<p data-ke-size="size16"> </p>
|
|
83
94
|
|
|
84
95
|
<!-- 4. Summary / Key Takeaways -->
|
|
85
96
|
<h2>핵심 정리</h2>
|
|
86
97
|
<ul>
|
|
87
|
-
<li>[Takeaway 1]</li>
|
|
98
|
+
<li>[Takeaway 1 — one complete sentence, not a fragment]</li>
|
|
88
99
|
<li>[Takeaway 2]</li>
|
|
89
100
|
<li>[Takeaway 3]</li>
|
|
90
101
|
</ul>
|
|
102
|
+
<p data-ke-size="size16"> </p>
|
|
91
103
|
|
|
92
|
-
<!-- 5. Closing (
|
|
93
|
-
<p>[Closing
|
|
104
|
+
<!-- 5. Closing (specific action the reader can take) -->
|
|
105
|
+
<p data-ke-size="size18">[Closing 1~2 sentences — suggest a concrete, immediate action. Not vague "stay tuned" but specific "try this tomorrow"]</p>
|
|
94
106
|
```
|
|
95
107
|
|
|
96
108
|
### Writing Rules
|
|
97
109
|
|
|
98
110
|
- **Title**: Include the primary keyword. 10~20 characters. Short and impactful.
|
|
99
|
-
- **
|
|
111
|
+
- **Length**: 3000~4000 characters (한글 기준). Aim for depth, not padding.
|
|
112
|
+
- **Paragraphs**: 3~5 sentences each. Develop ideas fully within a paragraph before moving on. Do NOT write 1~2 sentence paragraphs repeatedly.
|
|
113
|
+
- **Font size**: Use `<p data-ke-size="size18">` for all body text paragraphs. Use `<p data-ke-size="size16"> </p>` only for spacing between sections.
|
|
100
114
|
- **Spacing**: Use `<p data-ke-size="size16"> </p>` between sections for line breaks (Tistory-specific).
|
|
101
115
|
- **Hook**: Always use `<blockquote data-ke-style="style2">` for the opening topic quote.
|
|
102
|
-
- **
|
|
116
|
+
- **Introduction**: 2~3 paragraphs that set context and build reader empathy before diving into the body.
|
|
117
|
+
- **Body sections**: Each h2 section must have 2~3 substantial paragraphs. Do NOT jump straight to bullet lists.
|
|
118
|
+
- **Lists**: Use sparingly — only for 3+ concrete, scannable items. Default to paragraphs for explanation and analysis.
|
|
119
|
+
- **Evidence**: Each body section should include at least one of: expert quote, data point, real company example, or research finding. Cite sources naturally within the text.
|
|
120
|
+
- **Perspective shift**: Include at least one moment that reframes the reader's thinking (e.g., "X is not about A, it's about B").
|
|
121
|
+
- **Transitions**: Connect sections with bridge sentences. Avoid abrupt jumps between topics.
|
|
122
|
+
- **Bold**: Use `<strong>` for key terms and concepts (2~3 per section max).
|
|
103
123
|
- **Subheadings**: Use `<h2>` for ALL section titles. Do NOT use `<h3>`. Keep heading sizes consistent.
|
|
104
|
-
- **Tone**: Conversational but
|
|
105
|
-
- **
|
|
124
|
+
- **Tone**: Conversational but substantive. Write as if explaining to a smart colleague, not listing facts for a report.
|
|
125
|
+
- **Closing**: End with a specific, actionable suggestion the reader can try immediately — not a vague "stay tuned."
|
|
106
126
|
- **SEO**: Primary keyword in title, first paragraph, and at least one `<h2>`. Don't keyword-stuff.
|
|
107
127
|
|
|
108
128
|
```bash
|