@airmark/quiver 0.35.2 → 0.35.4
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/package.json
CHANGED
|
@@ -7,7 +7,7 @@ contacts:
|
|
|
7
7
|
- (333) 333-3333
|
|
8
8
|
- github.com/nibsbin
|
|
9
9
|
- linkedin.com/in/nibsbin/
|
|
10
|
-
-
|
|
10
|
+
- New New York
|
|
11
11
|
paper: us-letter
|
|
12
12
|
font_size: 11.5
|
|
13
13
|
margin: 0.5
|
|
@@ -41,24 +41,24 @@ skills:
|
|
|
41
41
|
~~~
|
|
42
42
|
$kind: experience
|
|
43
43
|
jobs:
|
|
44
|
-
- company:
|
|
44
|
+
- company: Planet Express Delivery Division
|
|
45
45
|
dates: August 2024 – Present
|
|
46
|
-
role:
|
|
47
|
-
location:
|
|
46
|
+
role: Interstellar Logistics Analyst
|
|
47
|
+
location: New New York
|
|
48
48
|
details: |-
|
|
49
|
-
- Analyzed
|
|
49
|
+
- Analyzed dark matter fuel combustion following the Nibblonian incident, developing safeguards to protect remaining ship engine infrastructure.
|
|
50
50
|
|
|
51
|
-
- Building automated
|
|
52
|
-
- company:
|
|
51
|
+
- Building automated hazard detection pipelines using Bender's antenna arrays to monitor Omicronian threat signatures across the sector.
|
|
52
|
+
- company: MomCorp Robotics Academy
|
|
53
53
|
dates: May 2025 – July 2025
|
|
54
|
-
role:
|
|
55
|
-
location:
|
|
56
|
-
details: "- Developed
|
|
57
|
-
- company:
|
|
54
|
+
role: Robot Firmware Trainee
|
|
55
|
+
location: Mars Vegas
|
|
56
|
+
details: "- Developed behavior-inhibitor firmware for MomCorp robots integrating real-time Slurm demand intelligence."
|
|
57
|
+
- company: DOOP Starship Nimbus
|
|
58
58
|
dates: January 2018 – June 2020
|
|
59
59
|
role: Combat Engineer
|
|
60
|
-
location:
|
|
61
|
-
details: "- Administrated
|
|
60
|
+
location: Vergon 6
|
|
61
|
+
details: "- Administrated Nimbus shipboard systems, Kif's maintenance logs, and killbot defense automation for 30,000+ crew."
|
|
62
62
|
title: Experience
|
|
63
63
|
~~~
|
|
64
64
|
|
|
@@ -7,7 +7,7 @@ contacts:
|
|
|
7
7
|
- (333) 333-3333
|
|
8
8
|
- github.com/nibsbin
|
|
9
9
|
- linkedin.com/in/nibsbin/
|
|
10
|
-
-
|
|
10
|
+
- New New York
|
|
11
11
|
paper: us-letter
|
|
12
12
|
font_size: 11.5
|
|
13
13
|
margin: 0.5
|
|
@@ -41,24 +41,24 @@ skills:
|
|
|
41
41
|
~~~
|
|
42
42
|
$kind: experience
|
|
43
43
|
jobs:
|
|
44
|
-
- company:
|
|
44
|
+
- company: Planet Express Delivery Division
|
|
45
45
|
dates: August 2024 – Present
|
|
46
|
-
role:
|
|
47
|
-
location:
|
|
46
|
+
role: Interstellar Logistics Analyst
|
|
47
|
+
location: New New York
|
|
48
48
|
details: |-
|
|
49
|
-
- Analyzed
|
|
49
|
+
- Analyzed dark matter fuel combustion following the Nibblonian incident, developing safeguards to protect remaining ship engine infrastructure.
|
|
50
50
|
|
|
51
|
-
- Building automated
|
|
52
|
-
- company:
|
|
51
|
+
- Building automated hazard detection pipelines using Bender's antenna arrays to monitor Omicronian threat signatures across the sector.
|
|
52
|
+
- company: MomCorp Robotics Academy
|
|
53
53
|
dates: May 2025 – July 2025
|
|
54
|
-
role:
|
|
55
|
-
location:
|
|
56
|
-
details: "- Developed
|
|
57
|
-
- company:
|
|
54
|
+
role: Robot Firmware Trainee
|
|
55
|
+
location: Mars Vegas
|
|
56
|
+
details: "- Developed behavior-inhibitor firmware for MomCorp robots integrating real-time Slurm demand intelligence."
|
|
57
|
+
- company: DOOP Starship Nimbus
|
|
58
58
|
dates: January 2018 – June 2020
|
|
59
59
|
role: Combat Engineer
|
|
60
|
-
location:
|
|
61
|
-
details: "- Administrated
|
|
60
|
+
location: Vergon 6
|
|
61
|
+
details: "- Administrated Nimbus shipboard systems, Kif's maintenance logs, and killbot defense automation for 30,000+ crew."
|
|
62
62
|
title: Experience
|
|
63
63
|
~~~
|
|
64
64
|
|
package/templates/templates.json
CHANGED
|
@@ -13,6 +13,13 @@
|
|
|
13
13
|
"file": "ussf_template.md",
|
|
14
14
|
"tags": ["space-force"]
|
|
15
15
|
},
|
|
16
|
+
{
|
|
17
|
+
"id": "usaf-letter",
|
|
18
|
+
"name": "USAF Personal Letter",
|
|
19
|
+
"description": "Official U.S. Air Force personal letter template",
|
|
20
|
+
"file": "usaf_letter.md",
|
|
21
|
+
"tags": ["air-force", "letter"]
|
|
22
|
+
},
|
|
16
23
|
{
|
|
17
24
|
"id": "rebuttal",
|
|
18
25
|
"name": "Rebuttal",
|
|
@@ -0,0 +1,48 @@
|
|
|
1
|
+
~~~card-yaml
|
|
2
|
+
$quill: usaf_letter@0.1
|
|
3
|
+
$kind: main
|
|
4
|
+
letterhead_title:
|
|
5
|
+
- DEPARTMENT OF THE AIR FORCE
|
|
6
|
+
- YOUR SQUADRON HERE
|
|
7
|
+
letter_from:
|
|
8
|
+
- Rank First M. Last
|
|
9
|
+
- Duty Title
|
|
10
|
+
- Unit Name
|
|
11
|
+
- Street Address
|
|
12
|
+
- City ST 12345-6789
|
|
13
|
+
letter_for:
|
|
14
|
+
- Rank First M. Last
|
|
15
|
+
- Duty Title
|
|
16
|
+
- Unit Name
|
|
17
|
+
- Street Address
|
|
18
|
+
- City ST 12345-6789
|
|
19
|
+
salutation: Dear Rank Last
|
|
20
|
+
complimentary_close: Sincerely
|
|
21
|
+
signature_block:
|
|
22
|
+
- FIRST M. LAST, Rank, USAF
|
|
23
|
+
tag_line: Aim High
|
|
24
|
+
$ext:
|
|
25
|
+
editor:
|
|
26
|
+
tips:
|
|
27
|
+
- Leave the date blank to sign and date the PDF by hand, or set it to the day you sign.
|
|
28
|
+
- Spell out the rank in the address lines (Major, not Maj) and write the salutation with no punctuation after the name.
|
|
29
|
+
- Paragraphs are not numbered; write them as plain prose.
|
|
30
|
+
~~~
|
|
31
|
+
|
|
32
|
+
<!--------------
|
|
33
|
+
In the data above, edit:
|
|
34
|
+
- Letterhead (your unit's full name below the first line)
|
|
35
|
+
- From (your rank, name, duty title, and mailing address)
|
|
36
|
+
- For (the recipient's rank, name, duty title, and mailing address)
|
|
37
|
+
- Salutation (for example, "Dear Major Smith")
|
|
38
|
+
- Signature block (your name in uppercase, grade, and service; no duty title)
|
|
39
|
+
---------------->
|
|
40
|
+
|
|
41
|
+
Open with the reason you are writing. A personal letter conveys official information in a personal manner, so write as you would speak to the reader.
|
|
42
|
+
|
|
43
|
+
Give the details in the paragraphs that follow. Keep each to one idea, and indent nothing yourself: the letter sets the first line of every paragraph in for you.
|
|
44
|
+
|
|
45
|
+
> Use a block quote for lines that should stay as written,\
|
|
46
|
+
> like a list of names or an address.
|
|
47
|
+
|
|
48
|
+
Close by telling the reader how to reach you, for example at DSN 555-0100 or first.last@us.af.mil.
|